docs(smoke): record the provisioned orchestrator and queue-target ids - #1800
Merged
Conversation
|
Azure Pipelines: 2 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Cutover provisioning is complete; recording the real ids and marking the runbook steps done. - released orchestrator registered as 2568 - executor-e2e queue target registered as 2569, verified green (build 629513), and E2E_QUEUE_PIPELINE_ID on 2550 repointed 2547 -> 2569 before 2547 is deleted - 2559 repointed at tests/smoke/azure-pipelines-candidate.yml with its six dead COMPILER_SMOKE_*_DEFINITION_ID variables removed in the same edit - SMOKE_LANE_AGENTIC_DEFINITION_ID=2567 on both orchestrators - pool 1453 and the service connections authorized on both new definitions 2568 and 2569 join scheduled_only_definition_ids so the policy audit covers them: both are scheduled or API-queued and must never acquire a CI or PR trigger. Drops the 2559-repoint warning, which has been actioned. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 323b70ff-d193-4c6e-b4c7-9ec6c3dc6ebd
…needs Fourth of five cases in the first live candidate run sat at notStarted forever with Checkpoint.Authorization inProgress and no logs. The multi-repo case checks out ado-aw-e2e-fixture via its repos: block, and a repository resource needs authorizing on the definition that consumes it - a separate grant from the agent pool and from the service connections, on a different resource type. The old per-case definitions had it (2544, 2564, 2565); the new lane inherited nothing, so exactly the one case with an extra checkout hung while the other four went green. This is the one piece of per-case ADO setup the lane model does NOT remove: a case adding a new repos: entry needs its repo authorized on the lane once, before that case can run. Documented in the runbook and, more usefully, in the case-authoring guide next to the other author-responsibility items - with the symptom spelled out, because a build with no logs gives no clue where to look. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 323b70ff-d193-4c6e-b4c7-9ec6c3dc6ebd
…ease gate Candidate mode is verified end to end. Build 629522 ran all five candidate cases on the single agentic lane, each on its own per-case ref, and reported Overall: PASSED. Afterwards the mirror holds only ado-aw-smoke-candidate-base and main, confirming per-case ref cleanup. That exercises the whole premise of the lane model: one definition, five refs, five distinct pipelines, no per-case registration. Released mode remains blocked, and not on anything configurable. It compiles with the last RELEASED binary, and v0.48.0 predates the change that made an absent on: emit explicit trigger: none / pr: none, so assertNoTriggers correctly rejects its output with 'staged pipeline must declare trigger: none, got null'. Reproduced locally against the real v0.48.0 asset. Cutting a release clears it; there is no fix to make here, which is why it is recorded as a gate rather than a bug. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 323b70ff-d193-4c6e-b4c7-9ec6c3dc6ebd
The plan doc was committed at the repository root so the redesign could be reviewed alongside the change, and its own header says to delete it once the cutover completes and the content has landed in tests/smoke/README.md. Both have now happened. Everything durable lives in the suite's own docs: the lane/ref model, modes, trigger handling and fork boundary in tests/smoke/README.md, and the definition ids, authorization steps and cutover runbook in tests/smoke/REGISTERED.md. What remains in the plan is design history - the before/after comparison and decision log - which is preserved in git history and in the #1791 description. Leaving it would be worse than removing it: it is a root-level file describing finished work as outstanding, and a second place where the remaining-cutover steps have to be kept in sync with REGISTERED.md. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 323b70ff-d193-4c6e-b4c7-9ec6c3dc6ebd
jamesadevine
force-pushed
the
docs/smoke-registered-ids
branch
from
August 4, 2026 19:34
8685bf7 to
3f72739
Compare
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
1 participant
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.
Cutover provisioning is complete. Records the real definition ids and marks the runbook steps done.
Also done: \2559\ repointed at \ ests/smoke/azure-pipelines-candidate.yml\ with its six dead \COMPILER_SMOKE_*_DEFINITION_ID\ variables removed in the same edit; \E2E_QUEUE_PIPELINE_ID\ on \2550\ moved \2547\ → \2569\ before \2547\ is deleted; \SMOKE_LANE_AGENTIC_DEFINITION_ID=2567\ on both orchestrators; pool \1453\ and the service connections authorized on both new definitions.
\2568\ and \2569\ join \scheduled_only_definition_ids\ so the policy audit covers them — both are scheduled or API-queued and must never acquire a CI or PR trigger.
Depends on nothing; #1799 fixes the audit bug that currently blocks the first released run.