Project

General

Profile

action #1812

Mechanism to synchronize the publishing of new ISOs/repos with the result of integration tests and for cleaning up results

Added by ancorgs over 8 years ago. Updated about 8 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
-
Target version:
Start date:
2014-03-06
Due date:
% Done:

50%

Estimated time:
10.00 h
Difficulty:

Description

In order to make "factory-tested" and "factory ISO" possible (see https://progress.opensuse.org/workflow/factory-proposal.html ), we need some way to 'stamp' a build as 'good enough' and a way to coordinate the publishing of new ISOs and repositories with that stamp.

History

#1 Updated by alarrosa over 8 years ago

  • Estimated time changed from 20.00 h to 30.00 h

#2 Updated by ancorgs over 8 years ago

  • Subject changed from Mechanism to synchronize the publishing of new ISOs/repos with the result of integration tests to Requirement for mechanism to synchronize the publishing of new ISOs/repos with the result of integration tests and for cleaning up results
  • Assignee set to coolo
  • Estimated time changed from 30.00 h to 10.00 h

#3 Updated by ancorgs over 8 years ago

  • Target version set to Sprint 04

#4 Updated by alarrosa over 8 years ago

  • Target version deleted (Sprint 04)

#5 Updated by alarrosa over 8 years ago

  • Assignee deleted (coolo)

#6 Updated by coolo over 8 years ago

  • Status changed from New to In Progress
  • Assignee set to coolo

Adrian recommends the following scenario:

openSUSE:Factory builds new ISOs without caring about build numbers per se - and publishes the FTP tree as factory_untested when it's ready.

an external entity checks if openQA is ready with the previous build and if openSUSE:Factory is ready with a new build (all ISOs built) and if so, triggers a "release" of openSUSE:Factory into openSUSE:Factory:ToTest and assigns a build number to all ISOs while copying the ISOs/repos.

openQA tests only staging projects and openSUSE:Factory:ToTest and once openQA is done with testing the build, the build is published and the previous step gets a green light to copy a new build.

OBS doesn't require new features to implement this, we'd need to implement the logic around it though.

#7 Updated by alarrosa over 8 years ago

  • Target version set to Sprint 06

#8 Updated by alarrosa over 8 years ago

  • Subject changed from Requirement for mechanism to synchronize the publishing of new ISOs/repos with the result of integration tests and for cleaning up results to Mechanism to synchronize the publishing of new ISOs/repos with the result of integration tests and for cleaning up results

#9 Updated by coolo over 8 years ago

  • % Done changed from 0 to 50

the solution is set out, but I had to fix several other things around factory ISOs to get closer to the goal of this issue

#10 Updated by coolo about 8 years ago

  • Status changed from In Progress to Resolved

will create more defined tasks

Also available in: Atom PDF