This remove pipeline steps needed during product development:
* Updating of release packages
* re-generation of 000product content
Re-add other staging letters.
Rather than using verify-repo-built-successful.py, check with
the API directly whether the product is blocked, scheduled or
building.
Since it might happen for a product being broken/failed (even after
a successful pkglistgen run), just fail in that case.
This is #3191, but for SUSE:SLFO:Main rather than 1.1.
Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
Rather than using verify-repo-built-successful.py, check with
the API directly whether the product is blocked, scheduled or
building.
Since it might happen for a product being broken/failed (even after
a successful pkglistgen run), just fail in that case.
Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
Stagings will be frozen iif:
- Check.Ring.1.Built job succeeds (runs every hour on Sundays, from 0 to 23. simple check and then exit)
- If the former check is successful, and it has not been freezed in the past day
Ensure that the 'product' repo is configured in the project meta.
Unfortunately, since we're checking in the configuration of the staging
itself, rather than the parent project's, there are increased changes of
some human/tooling error that might drop the repository from the
configuration. This will make the job run an endless loop.
Also, add a timeout for 180 minutes for the job. It is enough for
the product build process, and if it isn't, it's better to cancel
and have human eyes looking at it.
Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
During image testing, the artifacts built inside the 'product'
repository are used. Let's ensure that the repository is fully
built before attempting to enable images.
Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
