[pipeline] check-upgrade job should not depend on image build
With the fa90217a commit pipelines were reworked from parent-child to DAG. However needs relations have been slightly changed as compared to previous pipeline.
The check-upgrade-...
jobs in the new DAG pipeline depend on image-...
jobs
whereas they are do not depend in parent-child pipelines previously used.
As an input check-upgrade-...
jobs use image-stable-...
cache which should be fulfilled by the yield-...
jobs of the previous pipeline runs. Other input is an OSTree repository.
Several points makes such a configuration of pipeline to run notably longer:
-
check-upgrade-...
job should be run in parallel withcheck-install-...
and starts after it - usually it means to provision an additional instance which could take up to 10 minutes
- same time
check-upgrade-...
took a lot of time due to intensive disk image changes
The proposal is to exclude dependency on image-...
.
Thus image-...
and check-upgrade-...
jobs could start in parallel effectively reducing pipeline run time up to 5-10 minutes.
Another option is to swap check-install-...
and check-upgrade-...
jobs order in pipeline description. It not documented but it seems parallel jobs are started according to the order of their definition in pipeline configuration file. As a result check-upgrade-...
job could start first re-using instance previously used by image-...
job. But check-install-...
job would to start second and potentially could wait on the instance provisioning.