[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] eyal edri [Administrator] updated OVIRT-416: Assignee: eyal edri [Administrator] (was: infra) Status: In Progress (was: To Do) > [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: eyal edri [Administrator] > > 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.571.1#100021) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=22321#comment-22321 ] eyal edri [Administrator] commented on OVIRT-416: - Any patches sent on this? Also, wanted to mention #OVIRT-751 is handling similar purpose with enabling better maven caching, so it might suffice as a starting point in optimizing ovirt-engine runtime for builds. > [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.499.4#100018) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=20827#comment-20827 ] Vojtech Szocs commented on OVIRT-416: - > 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. +1 Full GWT build (all browsers & languages) is not needed for oVirt nightly (snapshot) builds. It's only needed for oVirt official (release) builds. > We are now adding the 'build official manual' option to standard CI, so we > can keep the 27 permutations there for official builds. Sounds good to me. > [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.319.1#100012) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
[
https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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#19)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=19039#comment-19039 ] eyal edri [Administrator] commented on OVIRT-416: - [~sbonazo...@redhat.com] [~mperina] do you know if today check-merged.sh in ovirt-engine is building the same RPMs as build-artifacts? Potentially they can be different since its a different bash script, but if they are the same we can save a lot of time running duplicate rpm builds... Now that we enabled GWT compilation per patch, maybe we can drop the rpm build on check-merged.sh and just do it in build-artifacts? we'll find an error in either jobs anyway.. what do you think? > [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.184.1#18) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Caro Estevez updated OVIRT-416: - Issue Type: Improvement (was: Bug) > [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 (v7.1.0-OD-06-005#71002) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
[JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
David Caro Estevez created OVIRT-416: Summary: [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: Bug 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 (v7.1.0-OD-06-005#71002) ___ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
