docs: poll Azure pipelines every 10 minutes - #2731
Rana Singh (ranadeepsingh) wants to merge 1 commit into
Conversation
## Summary Set a 10-minute polling cadence for long-running Azure builds in the SynapseML PR-loop skill and its CI triage reference. ## Prompting Intent The engineer requested a separate PR updating synapseml-pr-loop so that, after /azp run, it checks the pipeline every 10 minutes instead of making repeated short status checks. ## Linked Sources - Workflow: .github/skills/synapseml-pr-loop/SKILL.md - CI guidance: .github/skills/synapseml-pr-loop/references/ci-triage.md - Readiness helper: .github/skills/synapseml-pr-loop/scripts/Get-PrReadiness.ps1 - Readiness gates: .github/skills/synapseml-pr-loop/references/readiness-gates.md - Repository guidance: AGENTS.md - Related skill PR: microsoft#2730 ## Rationale Use explicit 600-second waits for pipeline completion, retaining the initial queue check and prompt handling of completion notifications. Keep review and check-registration polling separate because the readiness helper does not wait for full pipeline completion. Document the cadence rather than changing an unrelated helper default or adding a new monitoring script. Preserve the existing success gates and prohibit duplicate builds during status polling. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
Hey Rana Singh (@ranadeepsingh) 👋! We use semantic commit messages to streamline the release process. Examples of commit messages with semantic prefixes:
To test your commit locally, please follow our guild on building from source. |
|
/azp run |
|
Azure Pipelines: Successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The documentation is consistent with the readiness helper behavior and contains no blocking issues.
Review effort: Lite
Findings: None
What changed in this PR
Updates SynapseML PR-loop documentation to prescribe 10-minute Azure Pipeline polling while keeping readiness-helper polling separate.
Changes:
- Adds 600-second Azure build monitoring guidance.
- Documents queue verification, duplicate prevention, and post-completion result inspection.
- Clarifies
-PollSecondsdoes not control pipeline completion waits.
| File | Description |
|---|---|
.github/skills/synapseml-pr-loop/SKILL.md |
Adds polling cadence and readiness-loop guidance. |
.github/skills/synapseml-pr-loop/references/ci-triage.md |
Defines Azure monitoring and polling rules. |
💡 Configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
## Summary Replace the long contributor-review checklist with six practical steps and a short thank-you message. Reuse synapseml-pr-loop for shared validation. ## Prompting Intent The engineer asked to keep the skill simple and genuine, preserve all existing PR comments, and use synapseml-pr-loop instead of duplicating its workflow. They also asked to include the related polling change in the same PR. ## Linked Sources - Skill PR: microsoft#2730 - Polling PR to consolidate: microsoft#2731 - Existing workflow: .github/skills/synapseml-pr-loop/SKILL.md - Contributor example: microsoft#2710 (comment) ## Rationale Keep only the contributor-specific decisions here: independent triage, authorization, preserving their work and discussion, and thanking them after validation with a clear sign-off request and an offer to revert. Leave shared testing and CI detail in the PR-loop skill. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
|
Closing this because its 10-minute Azure pipeline polling guidance is now included in #2730. |
## Summary Replace the long contributor-review checklist with six practical steps and a short thank-you message. Reuse synapseml-pr-loop for shared validation. ## Prompting Intent The engineer asked to keep the skill simple and genuine, preserve all existing PR comments, and use synapseml-pr-loop instead of duplicating its workflow. They also asked to include the related polling change in the same PR. ## Linked Sources - Skill PR: microsoft#2730 - Polling PR to consolidate: microsoft#2731 - Existing workflow: .github/skills/synapseml-pr-loop/SKILL.md - Contributor example: microsoft#2710 (comment) ## Rationale Keep only the contributor-specific decisions here: independent triage, authorization, preserving their work and discussion, and thanking them after validation with a clear sign-off request and an offer to revert. Leave shared testing and CI detail in the PR-loop skill. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
## Summary Add a read-only Azure check monitor for synapseml-pr-loop and instructions to launch it as one attached background terminal process. ## Prompting Intent The engineer asked for token-efficient background monitoring so other work can continue, retaining 10-minute polling and setting a two-hour maximum. Keep the contributor skill short and update the existing combined PR. ## Linked Sources - Current skill PR: microsoft#2730 - Prior polling PR: microsoft#2731 - Existing readiness helper: .github/skills/synapseml-pr-loop/scripts/Get-PrReadiness.ps1 - CI guidance: .github/skills/synapseml-pr-loop/references/ci-triage.md - Repository guidance: AGENTS.md ## Rationale Run polling inside one process rather than spending model turns on status queries. Reuse GitHub CLI authentication and Azure check status already used by the readiness helper. Bind the monitor to the expected head and build so it cannot silently follow a different revision or retry. Bound both queries and sleeps by a monotonic deadline, report non-success explicitly, and never cancel or retrigger the remote build. Deterministic clock tests cover the full two-hour boundary without waiting in real time. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
## Summary Replace the long contributor-review checklist with six practical steps and a short thank-you message. Reuse synapseml-pr-loop for shared validation. ## Prompting Intent The engineer asked to keep the skill simple and genuine, preserve all existing PR comments, and use synapseml-pr-loop instead of duplicating its workflow. They also asked to include the related polling change in the same PR. ## Linked Sources - Skill PR: microsoft#2730 - Polling PR to consolidate: microsoft#2731 - Existing workflow: .github/skills/synapseml-pr-loop/SKILL.md - Contributor example: microsoft#2710 (comment) ## Rationale Keep only the contributor-specific decisions here: independent triage, authorization, preserving their work and discussion, and thanking them after validation with a clear sign-off request and an offer to revert. Leave shared testing and CI detail in the PR-loop skill. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
## Summary Add a read-only Azure check monitor for synapseml-pr-loop and instructions to launch it as one attached background terminal process. ## Prompting Intent The engineer asked for token-efficient background monitoring so other work can continue, retaining 10-minute polling and setting a two-hour maximum. Keep the contributor skill short and update the existing combined PR. ## Linked Sources - Current skill PR: microsoft#2730 - Prior polling PR: microsoft#2731 - Existing readiness helper: .github/skills/synapseml-pr-loop/scripts/Get-PrReadiness.ps1 - CI guidance: .github/skills/synapseml-pr-loop/references/ci-triage.md - Repository guidance: AGENTS.md ## Rationale Run polling inside one process rather than spending model turns on status queries. Reuse GitHub CLI authentication and Azure check status already used by the readiness helper. Bind the monitor to the expected head and build so it cannot silently follow a different revision or retry. Bound both queries and sleeps by a monotonic deadline, report non-success explicitly, and never cancel or retrigger the remote build. Deterministic clock tests cover the full two-hour boundary without waiting in real time. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
## Summary Replace the long contributor-review checklist with six practical steps and a short thank-you message. Reuse synapseml-pr-loop for shared validation. ## Prompting Intent The engineer asked to keep the skill simple and genuine, preserve all existing PR comments, and use synapseml-pr-loop instead of duplicating its workflow. They also asked to include the related polling change in the same PR. ## Linked Sources - Skill PR: microsoft#2730 - Polling PR to consolidate: microsoft#2731 - Existing workflow: .github/skills/synapseml-pr-loop/SKILL.md - Contributor example: microsoft#2710 (comment) ## Rationale Keep only the contributor-specific decisions here: independent triage, authorization, preserving their work and discussion, and thanking them after validation with a clear sign-off request and an offer to revert. Leave shared testing and CI detail in the PR-loop skill. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
## Summary Add a read-only Azure check monitor for synapseml-pr-loop and instructions to launch it as one attached background terminal process. ## Prompting Intent The engineer asked for token-efficient background monitoring so other work can continue, retaining 10-minute polling and setting a two-hour maximum. Keep the contributor skill short and update the existing combined PR. ## Linked Sources - Current skill PR: microsoft#2730 - Prior polling PR: microsoft#2731 - Existing readiness helper: .github/skills/synapseml-pr-loop/scripts/Get-PrReadiness.ps1 - CI guidance: .github/skills/synapseml-pr-loop/references/ci-triage.md - Repository guidance: AGENTS.md ## Rationale Run polling inside one process rather than spending model turns on status queries. Reuse GitHub CLI authentication and Azure check status already used by the readiness helper. Bind the monitor to the expected head and build so it cannot silently follow a different revision or retry. Bound both queries and sleeps by a monotonic deadline, report non-success explicitly, and never cancel or retrigger the remote build. Deterministic clock tests cover the full two-hour boundary without waiting in real time. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: dd10f95b-f7b6-49cc-9814-ac315de3aa8d
Related Issues/PRs
Companion workflow update to #2730. This PR is based directly on
masterand can merge independently.What changes are proposed in this pull request?
Update
synapseml-pr-loopto check queued or running/azp runbuilds every 10 minutes (600 seconds) rather than in short polling bursts.-PollSecondsdoes not control pipeline-completion waits, so its default stays unchanged./azp runcomments during polling and retain the requirement to inspect completed jobs and published test results.Only the skill and its CI triage reference change. No runtime code, scripts, workflow configuration, or dependencies change.
How is this patch tested?
Does this PR change any dependencies?
Does this PR add a new feature? If so, have you added samples on website?