fix: add agent pool + queue-id to initialise-project + ADO troubleshooting docs#143
Open
pgabriel-01 wants to merge 1 commit intoAzure:mainfrom
Open
fix: add agent pool + queue-id to initialise-project + ADO troubleshooting docs#143pgabriel-01 wants to merge 1 commit intoAzure:mainfrom
pgabriel-01 wants to merge 1 commit intoAzure:mainfrom
Conversation
…nes create The InitialiseProjectJob in initialise-project.yml had no pool block, causing the job to fail to schedule on freshly-provisioned ADO projects. Add 'pool: vmImage: ubuntu-latest' so it routes to the hosted pool. create_ado_pipelines.sh called 'az pipelines create' without --queue-id, which can fail with 'Could not queue the build' on new projects where the default queue association is not yet established. Resolve the queue ID dynamically by name (default 'Azure Pipelines'), with AGENT_POOL_NAME env var override for self-hosted pools. Also add a Troubleshooting section to deployguide_ado.md covering the most common failure modes reported by accelerator users: - Hosted parallelism not granted (aka.ms/azpipelines-parallelism-request) - Missing 'Create build pipeline' permission - Stale folders/repos blocking initialise-project retry - Retired ubuntu-20.04 image - Queue association failure on new projects Reported by Vicky Arpatzoglou via accelerator feedback.
mahalaxminanya
approved these changes
May 6, 2026
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.
PR Summary into Azure/mlops-v2
Checklist
I have:
Changes
Three related fixes for issues users hit when running
initialise-projecton a freshly-provisioned Azure DevOps organization.1.
initialise-project.yml— missing agent poolInitialiseProjectJobhad nopool:block. ADO falls back to the org's default pool, which on new orgs may be unset, causing the job to fail to schedule. Added explicit:2.
create_ado_pipelines.sh— missing--queue-idaz pipelines createwas called without--queue-id. On newly-provisioned projects this can fail with"Could not queue the build because there were validation errors or warnings"because the default queue-to-pool association is not yet established.Fix: resolve the queue ID dynamically by pool name before the loops:
Both
az pipelines createcalls now pass${queue_id:+--queue-id $queue_id}(the parameter is omitted gracefully if the lookup fails, preserving backward compatibility). Self-hosted pool users can override via theAGENT_POOL_NAMEenvironment variable.3.
deployguide_ado.md— Troubleshooting sectionAdded a new Troubleshooting section before Next Steps in MLOps, covering the five most common failure modes reported by users:
initialise-project.ubuntu-20.04image — pointer to fix inmlops-project-template.Testing
bash -n .azuredevops/scripts/create_ado_pipelines.sh— syntax OK.${queue_id:+--queue-id $queue_id}expansion verified to expand only when set.Merge note
Requesting squash and merge.
Reported by Vicky Arpatzoglou via accelerator feedback (initialise-project failures, parallelism, build-pipeline permissions, stale folders, ubuntu-20.04 image).
fixes #