[
https://ovirt-jira.atlassian.net/browse/OVIRT-1315?page=com.atlassian.jir...
]
Barak Korren commented on OVIRT-1315:
-------------------------------------
[~sbonazzo(a)redhat.com] That will probably require rewriting STC-CI jobs to be 'Jenkins
Pipeline' jobs. This may be the long term solution but its is a considerable rewrite,
so we are not eager to go down that road just yet. One downside of this is that the
project-specific YAML files will probably have to change, unless we also get to
implementing OVIRT-1013.
I'm hoping we can find some trick to make "deploy to experimental" figure
out there are still some more build jobs for the same commit running and wait for them. We
will probably need to rewrite it too, but I'm thinking this may be a simpler and less
visible rewrite then for 'build artifacts'. I may be wrong about that though.
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)