[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any

[eyal edri [Administrator] (oVirt JIRA)]

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

eyal edri [Administrator] commented on OVIRT-416:
-------------------------------------------------

OK,
looking at the code it seems check-merged is running a draft build:

# create the rpms
rpmbuild \
    -D "_rpmdir $PWD/output" \
    -D "_topmdir $PWD/rpmbuild" \
    -D "release_suffix ${SUFFIX}" \
    -D "ovirt_build_ut $BUILD_UT" \
    -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \
    -D "ovirt_build_draft 1" \
    --rebuild output/*.src.rpm

while build artifacts is running full blown matrix:

# create the rpms
rpmbuild \
    -D "_rpmdir $PWD/output" \
    -D "_topmdir $PWD/rpmbuild" \
    -D "release_suffix ${SUFFIX}" \
    -D "ovirt_build_ut $BUILD_UT" \
    -D "ovirt_build_extra_flags $EXTRA_BUILD_FLAGS" \
    --rebuild output/*.src.rpm

and currently running 27(!) permutations.

So the question is, can we reduce this to 1-2 permutations? if this is just going to nightly / hourly repo then we don't need all these permutations and we'll enjoy a much faster verification on the experimental flow which collects artifacts from build-artifacts jobs.

We are now adding the 'build official manual' option to standard CI, so we can keep the 27 permutations there for official builds. 

I believe this will reduce dramatically the CI flow runtime and will give us much faster feedback on failures.

Also, it will simplify the move to running experimental flow per patch as the full run-time will be significantly lower.




> [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
> -------------------------------------------------------------------------------------
>
>                 Key: OVIRT-416
>                 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416
>             Project: oVirt - virtualization made easy
>          Issue Type: Improvement
>            Reporter: David Caro Estevez
>            Assignee: infra
>
> Right now most projects just rebuild twice the artifacts, what for some means a big waste of resources, if we could just reuse what was built previously there would be no rebuilding.
> Something to take into account is that the distributions that check-merged and build-artifacts run for might not match, so you can be running check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as an example), maybe we should not allow different distros on each stage?|



--
This message was sent by Atlassian JIRA
(v1000.245.0#100009)