Since the switch to Git backed sources for SL-Micro 6.0, staging
workflow does not work anymore for SUSE:ALP:Products:Marble:6.0. This
patch drops all related pipelines. Additional it adds the same checkers
for the SUSE:SLFO:Main project.
This remove pipeline steps needed during product development:
* Updating of release packages
* re-generation of 000product content
Re-add other staging letters.
After the latest changes of product-composer (allowing to build isos with different
names than ftp trees), the sbom assets are no longer saved in the root of the repo
(as they are for SLFO 1.0) and now live in the iso folder as well.
So look for those assets in both places.
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>
- Rename SLFO.Standard to SLFO.Snapshot
- Fix SLFO_BUILD_PROJECT, must be SUSE:SFLO:Main:Build where the binaries
to be released to SUSE:SLFO:Main:Build:Snapshot are stored
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
This allows to always publish from :TEST to :PUBLISH even without
the :GA -> :TEST step.
Useful for when gocd cleans up old pipeline runs.
Signed-off-by: Eugenio Paolantonio <eugenio.paolantonio@suse.com>
