Serialize long-running webhook actions - #37
Open
Lun Yue (lunyue-ms) wants to merge 9 commits into
Open
Conversation
Keep the Node.js event loop responsive while processing concurrent GitHub webhook deliveries. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Refresh credentials at execution time, bound pending work, and keep retry and telemetry paths from blocking webhook processing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
Azure Pipelines can reject /azp run while the latest PR revision is still synchronizing. Match the other automation paths with a 10-second delay. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
Keep webhook responses below GitHub timeout while delaying Azure triggers. Skip stale or closed PR revisions and deduplicate pending comments. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
Report detected and existing sync conflicts as action-required checks so GitHub shows an orange intervention state while required checks remain blocking. Keep unexpected errors as failures. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
Revert the global action-required mapping because it affects every ms_conflict check, not only the code-sync pipeline. This reverts commit dbc80ae. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
Retry an automatically issued /azp run once when Azure has not yet registered the unchanged PR revision. Skip retries after revision changes, merge conflicts, or a validation start. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
Remove the stale-comment retry flow and give Azure more time to register the pull request revision before issuing /azp run. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: Lun Yue <17232861+lunyue-ms@users.noreply.github.com>
Contributor
|
/azp run |
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
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.
Why I did it
Concurrent webhook deliveries can start multiple long-running GitHub and Azure DevOps actions at the same time. Synchronous child processes block the Node.js event loop, while overlapping handlers can lose or corrupt work.
ADO: https://msazure.visualstudio.com/One/_workitems/edit/39378257
How I did it
/azpw retryrequests and replace blocking ADOcurlcalls with asynchronous HTTPS requests.How to verify it
Result: 2 test suites and 5 tests passed.