Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deployments: canary=0 is implicitly autopromote #11013

Merged
merged 3 commits into from
Aug 10, 2021
Merged

Conversation

notnoop
Copy link
Contributor

@notnoop notnoop commented Aug 7, 2021

In a multi-task-group job, treat 0 canary groups as auto-promote.

This change fixes an edge case where Nomad requires a manual promotion,
if the job had any group with canary=0 and rest of groups having
auto_promote set.

Fixes #8139

In a multi-task-group job, treat 0 canary groups as auto-promote.

This change fixes an edge case where Nomad requires a manual promotion,
if the job had any group with canary=0 and rest of groups having
auto_promote set.
@notnoop notnoop requested review from schmichael and jrasell August 7, 2021 01:54
@notnoop notnoop self-assigned this Aug 7, 2021
@schmichael schmichael changed the title deployments: canary=0 is implicitly autorpomote deployments: canary=0 is implicitly autopromote Aug 9, 2021
nomad/structs/structs.go Show resolved Hide resolved
Co-authored-by: Michael Schurter <[email protected]>
@vercel vercel bot temporarily deployed to Preview – nomad August 10, 2021 20:32 Inactive
@notnoop notnoop merged commit dfb313a into main Aug 10, 2021
@notnoop notnoop deleted the b-implicit-auto-promote branch August 10, 2021 21:06
notnoop pushed a commit that referenced this pull request Aug 26, 2021
In a multi-task-group job, treat 0 canary groups as auto-promote.

This change fixes an edge case where Nomad requires a manual promotion,
if the job had any group with canary=0 and rest of groups having
auto_promote set.

Co-authored-by: Michael Schurter <[email protected]>
notnoop pushed a commit that referenced this pull request Aug 26, 2021
In a multi-task-group job, treat 0 canary groups as auto-promote.

This change fixes an edge case where Nomad requires a manual promotion,
if the job had any group with canary=0 and rest of groups having
auto_promote set.

Co-authored-by: Michael Schurter <[email protected]>
@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Canary AutoPromote fails when non-canary taskgroups exist
2 participants