[ https://ovirt-jira.atlassian.net/browse/OVIRT-1124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
eyal edri [Administrator] updated OVIRT-1124: --------------------------------------------- Epic Link: OVIRT-411 > Automate oVirt official release process > --------------------------------------- > > Key: OVIRT-1124 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1124 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: eyal edri [Administrator] > Assignee: infra > > Current release flow is 100% manual and depends on multiple sources of built > RPMs. > We should support one automated flow which will use the standard CI to build > and publish official oVirt releases. > Some initial thoughts to consider: > * We'll need to trigger 'build-artifacts' job when a new tag is added to > project and build the official release ( in ovirt-engine we do it already > with a special if in build-artifacts.sh ) > * The new RPMS should pass OST / Experimental verification and deployed to > 'pre' repo after verification. > * We should support only this flow and not external build systems like > koji/copr, any project maintainer that still wants to build in other system > is welcome, but for oVirt repos we'll do it from the official tag > * Consider using repoman for signing the RPMs when we compose the 'pre' repo > * If a project doesn't have a new tag to build from, we'll use the latest > official release of that project. > [~bkor...@redhat.com][~amarchuk][~sbonazo...@redhat.com] thoughts? -- This message was sent by Atlassian JIRA (v1000.747.0#100028) _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra