Refactor metadata publishing to use async/await and improve setResult error handling #21703
+26
−19
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
ivanduplenskikh
force-pushed
the
users/iduplenskikh/PublishPipelineMetadata-set-correct-result
branch
from
99a66c8 to
582d6ba
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
ivanduplenskikh
force-pushed
the
users/iduplenskikh/PublishPipelineMetadata-set-correct-result
branch
from
582d6ba to
28ad8d0
Compare
Contributor
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
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
Ensure metadata publish requests complete before the task finishes, and surface non-2xx failures.
Task Name
PublishPipelineMetadataV0
Description
Risk Assessment (Low / Medium / High)
Low - scoped to async handling and response validation in a single task.
Change Behind Feature Flag (Yes / No)
TBD
Tech Design / Approach
Documentation Changes Required (Yes/No)
No.
Unit Tests Added or Updated (Yes / No)
No.
Additional Testing Performed
TBD
Logging Added/Updated (Yes/No)
No — existing debug logging only adjusted.
Telemetry Added/Updated (Yes/No)
No.
Rollback Scenario and Process (Yes/No)
Yes — revert this commit.
Dependency Impact Assessed and Regression Tested (Yes/No)
Yes — no dependency changes.
Checklist