Canary Task Rollouts #21160
Merged
Canary Task Rollouts #21160
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/azp run |
|
/azp run |
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
reviewed
Jul 23, 2025
merlynomsft
approved these changes
Jul 23, 2025
merlynomsft
approved these changes
Jul 23, 2025
|
/azp run |
2 similar comments
|
/azp run |
|
/azp run |
tarunramsinghani
approved these changes
Jul 30, 2025
tarunramsinghani
approved these changes
Aug 4, 2025
sanjuyadav24
force-pushed
the
users/sanjuyadav/canary_testing_1
branch
from
d40bb7c to
74f44b0
Compare
|
/azp run |
1 similar comment
|
/azp run |
tarunramsinghani
approved these changes
Aug 6, 2025
tarunramsinghani
approved these changes
Aug 6, 2025
added 6 commits
August 12, 2025 12:13
sanjuyadav24
force-pushed
the
users/sanjuyadav/canary_testing_1
branch
from
00fb344 to
cb6ae04
Compare
|
/azp run |
|
Azure Pipelines failed to run 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines failed to run 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines failed to run 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines failed to run 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines failed to run 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
rishabhmalikMS
approved these changes
Aug 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
This shows the changes that we must make on the pipeline tasks side to allow canary rollouts
A new release field is added which will be used on server side for canary rollout
"release": {
"sprint": 259,
"ordinal": 1
}
The Sprint corresponds to the current sprint number (259 in this case), and the Ordinal is a sequence number.
When [useSemverBuildConfig = false]
Tasks generated with traditional versioning (different patch numbers)
No breaking changes to existing functionality
Example: PowerShellV2: 2.259.0, PowerShellV2_Node20: 2.259.1
When [useSemverBuildConfig = true]
All task configs share the same major.minor.patch version
Non-default configs get build suffixes from their constMappingKey
Default config has no build suffix
Example: PowerShellV2: 2.259.0, PowerShellV2_Node20: 2.259.0+Node20-225
Task Name
NA
Description
This shows the changes that we must make on the pipeline tasks side to allow canary rollouts. Adds a new field release in the task to associate task with sprint versions
Risk Assessment (Low / Medium / High)
Low (Flag based check, for older task no changes are required)
Unit Tests Added or Updated (Yes / No)
No ( changes are in task build process)
Additional Testing Performed
Manual testing to generate tasks in new format
Documentation Changes Required (Yes / No)
Yes
Checklist