[
https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29811#comment-29811
]
sbonazzo commented on OVIRT-1315:
---------------------------------
[[email protected]] can we change stdci to have a single build job that
trigger all the different distro/arch builds, wait until they finishes and then
finish with success if all succeeded and trigger the deploy job?
This is valid for all projects, not only vdsm. It doesn't make sense to have
different versions/builds available for different arches/distro.
> post-merge build-artifacts jobs for the same commit have a race condition
> between different platforms
> -----------------------------------------------------------------------------------------------------
>
> Key: OVIRT-1315
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1315
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
> Priority: High
>
> When a change is merged the build artifacts jobs for all platforms are
> invoked in parallel by the Gerrit trigger. These jobs in turn invoej the
> 'deploy-to-experimental' job to move the artifacts into the 'experimental'
> repos for OST testing.
> Various issues arise because of this:
> # A Fedora build can trigger an OST run befire the equivalent EL7 build
> finishes. This wastes resources on needless OST runs.
> # A PPC64 build can place 'noarch' artifacts in experimental before the
> equivalent x86_64 builds are ready. This can cause OST failures.
> Because of the PPC64 issue, we have actually disabled publishing into
> experimental from the PPC64 jobs. Since we now want to move to fully
> automated production publishing via the experimental flow, we need to fix
> this.
--
This message was sent by Atlassian JIRA
(v1000.892.1#100040)
_______________________________________________
Infra mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/infra
