Improve checks on folding/branching

Background

As explained in apertis-infrastructure!216 (comment 150760) the folding and branching pipelines should help to identify potential issues, like packages which have not reached the APT repos, to avoid releasing unhealty images.

Outcomes

TBD

Management data

This section is for management only, it should be the last one in the description.

/cc @em @Balasubramanian @sudarshan @wlozano

Phabricator link: https://phabricator.apertis.org/T10872

added priority:needs triage release:v2023 release:v2024 release:v2025pre status:unconfirmed labels

mentioned in merge request apertis-infrastructure!216 (merged)

changed the description

added priority:normal label and removed priority:needs triage label

Just to confirm this issue, while removing go/rust from v2024:development because of the move to v2024:target. I faced some issues because some pipelines due to the folding of v2024 failed therefor some packages (~ 3-4) haven't reached OBS.

Yes, after the folding in complete we should have a stage to check with the dashboard that pipelines are OK and the all then cleanups have been done.

What about apertis-infrastructure!232 (merged)

Merged! Thanks, this job makes sense since it is similar to the manual checks we have at the end of the branching.

removed release:v2024 label

removed release:v2023 label

removed release:v2025pre label