[ https://ovirt-jira.atlassian.net/browse/OVIRT-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19841#comment-19841 ] eyal edri [Administrator] commented on OVIRT-414: ------------------------------------------------- I think it will just prolong significantly our output from experimental flows without a major benefit. we now have enough slaves and jenkins power to handle both builds in parallel so I don't see benefit in doing this, we should invest in improving our infra and adding slaves if needed. also, there is another ticket that talks about not building ALL permutations on build_artifacts for ovirt-engine and only doing that for official builds. see https://ovirt-jira.atlassian.net/browse/OVIRT-416 for more info

[standard-ci] build stage should start only after check-merged stage completes ------------------------------------------------------------------------------

Key: OVIRT-414 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-414 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Affects Versions: Production Reporter: sbonazzo Assignee: infra

In order to save jenkins resources, build stage should be triggered only after check-merged stage passes.

-- This message was sent by Atlassian JIRA (v1000.253.3#100011)