search

lucabello / noctua

Helper tool for Canonical's Observability CI.
Apache License 2.0
0 stars 0 forks source link

Add a way to block the promotion of a particular release in the promotion train #4

Open ca-scribner opened 1 week ago

ca-scribner commented 1 week ago

The promotion train always promotes all release charms, but sometimes this isn't what we want. For example, if a bug is caught in candidate, running the promotion train will push that bug to stable. This has happened several times in the past few months, propagating known bugs into the stable branch of our charms

We need a way to indicate when a release should never be promoted further. Conceptually, I should be able to do something (add a tag, or some other metadata in our gh repo?) that prevents out CI from promoting that revision further. That way we can see a bug, freeze the release(s) it affects, and still safely use the promotion train for everything else.

lucabello commented 1 week ago

This would be great to have; any idea for what we could use? Using repository tags seems like we're abusing their semantics, and I'm not aware of other metadata we can use for this :(