You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Promotions and Verifications run at mutually exclusive points in time (e.g. when verification is happening, promotion does not and vice versa). Sometimes, new Freight might appear at a faster rate than can be verified. This might happen automatically -- if many image builds are produced quickly, but the analysis template is long-running. When this happens, the Stage will queue the Promotion job, which then might accumulate on the Stage:
Kargo could offer a feature that would allow a later promotion to cancel all currently Pending promotions so that when the new Promotion is created, it will be the next one to run.
Motivation
I think a common desire will be that a later Freight is the only one that matters to be verified and that intermediate versions be skipped (in terms of deploying into the Stage as well as being verified).
Suggested Implementation
We should support this manually as well as automatically. e.g. in the manual case, the UI/API could have an option to supersede the Pending promotions, and offer a checkbox to cancel them before creating the later one.
Stage and/or Projects should introduce a promotion policy preference with a "supersede" option.
If "supersede" is true, Pending promotions will be canceled before creating the new Promotion resource
Even though this will be a spec field in Stage and/or Project, the UI/API should still have the ability to override the Project/Stage setting and explicitly choose to supersede or queue the Promotion. (e.g. sometimes user might want to occasionally queue up a bunch of different Freight to be verified).
The text was updated successfully, but these errors were encountered:
Proposed Feature
Promotions and Verifications run at mutually exclusive points in time (e.g. when verification is happening, promotion does not and vice versa). Sometimes, new Freight might appear at a faster rate than can be verified. This might happen automatically -- if many image builds are produced quickly, but the analysis template is long-running. When this happens, the Stage will queue the Promotion job, which then might accumulate on the Stage:
Kargo could offer a feature that would allow a later promotion to cancel all currently Pending promotions so that when the new Promotion is created, it will be the next one to run.
Motivation
I think a common desire will be that a later Freight is the only one that matters to be verified and that intermediate versions be skipped (in terms of deploying into the Stage as well as being verified).
Suggested Implementation
We should support this manually as well as automatically. e.g. in the manual case, the UI/API could have an option to supersede the Pending promotions, and offer a checkbox to cancel them before creating the later one.
The text was updated successfully, but these errors were encountered: