[ https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira... ] 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. -- This message was sent by Atlassian JIRA (v1000.245.0#100009)