[JIRA] (OVIRT-1252) post-merge build-artifacts jobs can run out of order

[eedri (oVirt JIRA)]

    [ https://ovirt-jira.atlassian.net/browse/OVIRT-1252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33163#comment-33163 ] 

eedri commented on OVIRT-1252:
------------------------------

[~bkorren at redhat.com] is this still relevant after the deployment of the new logic of deploy rpms?

> post-merge build-artifacts jobs can run out of order
> ----------------------------------------------------
>
>                 Key: OVIRT-1252
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1252
>             Project: oVirt - virtualization made easy
>          Issue Type: Bug
>            Reporter: Barak Korren
>            Assignee: infra
>              Labels: standard-ci
>
> Right now build-artifacts jobs that run post merge get run on every patch and are allowed to run in parallel.
> The end result of this is that they do not always finish in the same order in which the patches were merged. This ends up causing the latest build link in Jenkins to not always point to the real latest build. It may also means that packages get pushed to OST not in the right order.
> To fix this we need to make sure the build-artifacts jobs do not run in parallel. Alternatively we could split the build artifacts job into a trigger job and a builder job where the trigger job gets run on every patch in parallel and the builder job only runs where resources are available.



--
This message was sent by Atlassian JIRA
(v1000.1092.1#100053)