Protect base image in development branches
It is very important for the release process that the CI base image is the correct one.
By definition, it cannot be done in the release branch, because the CI base image is used in them precisely to know which of the development branches it currently relates to.
The main sources of unwanted changes being merges from heptapod-stable
to heptapod
(creeping only afterwards to the release branches)
Ideas:
- adding a protection for the development branches (as part of CI jobs) would catch most of them. Usually those merges don't go through CI, but knowing slowly after the fact is perhaps good enoug.
- create a precommit hook and deploy it through HDK. Caveat: In my case, the faulty merges could happen outside of HDK context. Thankfully, I have only a couple non-HDK clones (shares, actually).