Manually created freight shouldn't be auto promoted to a stage that directly sources from the warehouse #3162
Unanswered
aayushsrivastava
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a 3-stage pipeline: QA -> UAT -> Prod
The docker images use SemVer-based tags and its Warehouse has auto freight creation enabled. Auto promotion is also enabled for the QA stage. With this setup, all the latest images built from the trunk automatically land on QA. UAT and Prod promotions are manual.
I am trying to implement a hotfix workflow where the version of the hotfix will be lower than the trunk. For example, the trunk may be v2.1.0, the hotfix will be v1.0.1. I don't want the hotfix to auto-promote to QA. Instead, I will manually approve it from promotion to UAT and then Prod.
Currently, the hotfix doesn't auto-promote to QA (perhaps because no freight gets automatically created because its version is lesser than the latest version). This is the correct behavior for us. We can create freight manually for hotfixes.
However, when I create the freight manually, it is auto-promoted to QA which is not a desired behavior as I will now have to manually restore QA to the image built from trunk. Can we somehow stop the manually created freights from being auto-promoted to QA in this case?
Beta Was this translation helpful? Give feedback.
All reactions