Project

General

Profile

Actions

action #2520

closed

Implement Factory-Tested Manager

Added by coolo over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2014-05-26
Due date:
% Done:

100%

Estimated time:
(Total: 32.00 h)

Description

Right now we have 2 tasks that are manual work but shouldn't be:

  1. Update Factory:Test
    • if previous snapshot is done testing (to be defined what this means, but basically: if there is no point continue testing)
    • if openSUSE:Factory repos are all published/unpublished without being dirty
    • if openSUSE:Factory:Live is all published without being dirty
    • if there is no successful snapshot of today

-> then we call set_release with a Snapshot, which will trigger the release of openSUSE:Factory and openSUSE:Factory:Live into openSUSE:Factory:ToTest

  1. Publish openSUSE:Factory:ToTest
    • if the current snapshot in FTT is good enough (to be defined), we need to
    • change to in ToTest/_meta
    • wait for the repo to switch from unpublished to published (can take hours unfortunately)
    • change _meta back to <disable

These 2 tasks need to run in a loop

I expect several subtasks to be in need - e.g. to define what it means to be "good enough in testing"


Subtasks 6 (0 open6 closed)

action #2550: Function to check current snapshot on openqaResolvedcoolo2014-05-26

Actions
action #2552: Check factory stateResolvedcoolo2014-05-26

Actions
action #2554: pythonize set_release.shResolvedcoolo2014-05-26

Actions
action #2556: Implement function to change publish flag in ToTest prjResolvedcoolo2014-05-26

Actions
action #2558: Implement function to check isosize of factory isosResolvedcoolo2014-05-26

Actions
action #2562: Implement actual work flow of the tested managerResolvedcoolo2014-05-26

Actions
Actions #1

Updated by aplanas over 10 years ago

  • Target version set to Staging sprint 08
Actions #2

Updated by coolo over 10 years ago

  • Assignee set to coolo
Actions #3

Updated by coolo over 10 years ago

before we release, we can check at least the isosize.

Actions #4

Updated by coolo over 10 years ago

I reconsidered the 2nd step. There is no need to wait for the published state. We can leave the prj in publish enabled all day - as long as we disable it before we call a snapshot, i.e. in step 1.

Actions #5

Updated by coolo over 10 years ago

  • Target version deleted (Staging sprint 08)
Actions #6

Updated by coolo over 10 years ago

  • Status changed from New to Resolved
  • Target version set to Staging sprint 09

done

Actions

Also available in: Atom PDF