[JIRA] (OVIRT-1699) Add a 4.2 CQ flow

This is a multi-part message in MIME format... ------------=_1508255798-16611-740 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1699?page=com.atlassian.jira.p... ] Barak Korren reassigned OVIRT-1699: ----------------------------------- Assignee: Barak Korren (was: infra) Issue Type: New Feature (was: Task)
Add a 4.2 CQ flow ------------------
Key: OVIRT-1699 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1699 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: eyal edri Assignee: Barak Korren
As discussed, we need to start preparing a 4.2 flow for CQ so projects which branched for 4.2 will be able to publish their artifacts and also to start preparing the work for the stable branch of 4.2 due in the coming months. Initial work for running OST On 4.2 is done via: https://gerrit.ovirt.org/#/c/81969/ Which is basically a clone of 4.1, with empty 4.2 tested repo for now ( disabled for now ). Once we start getting more and more projects into the 4.2 branch, we can also move to run 4.2 tests ( which will fail now because they need code from master )
-- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100066) ------------=_1508255798-16611-740 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1699?page=com.atlassian.jira.p... ]</pre> <h3>Barak Korren reassigned OVIRT-1699:</h3> <pre> Assignee: Barak Korren (was: infra) Issue Type: New Feature (was: Task)</pre> <blockquote><h3>Add a 4.2 CQ flow</h3> <pre> Key: OVIRT-1699 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1699 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI Reporter: eyal edri Assignee: Barak Korren</pre> <p>As discussed, we need to start preparing a 4.2 flow for CQ so projects which branched for 4.2 will be able to publish their artifacts and also to start preparing the work for the stable branch of 4.2 due in the coming months. Initial work for running OST On 4.2 is done via: <a href="https://gerrit.ovirt.org/#/c/81969/">https://gerrit.ovirt.org/#/c/81969/</a> Which is basically a clone of 4.1, with empty 4.2 tested repo for now ( disabled for now ). Once we start getting more and more projects into the 4.2 branch, we can also move to run 4.2 tests ( which will fail now because they need code from master )</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100066)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BCmpYLyzY..." alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1508255798-16611-740--
participants (1)
-
Barak Korren (oVirt JIRA)