Feature changed by: Adrian Schröter (adrianSuSE) Feature #311785, revision 3 Title: release handling (in general and for maintenance incidents in special) Buildservice: New Milestone: 2.3 Priority Requester: Mandatory Requested by: Adrian Schröter (adriansuse) Engineering Manager: (Novell) Technical Contact: (Novell) Partner organization: openSUSE.org Description: We have the need to manage releases in OBS. Releases in this context are entire builds, which can be tested at one place and can be moved afterwards to another place (project and/or repository). We have this need for * Maintenance releases * Factory standard -> snapshot releases * anything else ? The release target shall be defined in the repository defintion of the origin repository. For example <project name="myProject"> ... <repository name="standard"> <path.... <releasetarget project="myProject" repository="snapshot" condition=" - repositoryfinished|buildsuccessful|manual|maintenance" /> + finished|allsucceeded|manual|maintenance" /> ... The conditions define when the release happens: - * repositoryfinished: Always, after the "standard" repository finished, - the releasetarget gets updated (may be usefull as "blocked" - workaround). - * buildsuccessful: Release only when no failed/unresolvable/broken build + * finished: Always, after the "standard" repository finished, the + releasetarget gets updated (may be usefull as "blocked" workaround). + * allsucceeded: Release only when no failed/unresolvable/broken build state exists. * manual: release on manual command by the user. * maintenance: release happens on maintenance_release accept event. The accept is also removing the condition attribute. It can be added again, in case an incident needs to get restarted/re-released. * no condition attribute: do not do anything. it is just kept to define the target (maybe this would be the manual case ?) -- openSUSE Feature: https://features.opensuse.org/311785