Skip to content

Packaging: fixing determination of target branch in omnibus-heptapod

The previous ancestry-based criterion had a major drawback: it didn't work in case heptapod-stable is fully merged into heptapod.

Rather than playing with more hazardeous logic for this script part that is only tested at release time, we choose here to rely on the fact that the stable status has already been manually set in the CI configuration file, in the form of the base image to use.

Of course, this can also be wrong, but in that case we should already have encountered other issues. In truth, we should also think of a mechanism to guarantee that the base CI image is the correct one, but that can be done independently (as a check in pipelines of the heptapod-stable and heptapod branches, for instance).

Merge request reports