Reputation: 1286
When creating a new Pipeline in Azure DevOps projects, for one of our Azure projects, I don't get the option to select an existing yaml file. I've compared settings with our different projects but I don't understand why the wizard jumps straight past the Configure option without ability to go back.
Specifically, after creating "New pipeline"->"Azure Repos Git"->"Select a repository" the wizard jumps straight past the Configure option to Review tab. At this point I only get the option to review my YAML file (and rename the file - no option to pick branch or existing file).
The configure screen options I'm expecting but don't get:
Any ideas why this would only be happening for certain Azure DevOps projects/repos??
Note: I have an existing yaml pipeline already in this Git repo (so do the other projects) - but even for the first pipeline I had to stuff around creating/editing/saving this file based on the default "starter pipeline" yaml file.
Upvotes: 2
Views: 2537
Reputation: 1263
I had this issue and fixed it by uploading the azure-pipelines.yml file to the main branch - I could then select it. Initially I just had the yml file in my releases branch.
Upvotes: 0
Reputation: 1583
Step 1: Go through all the way to the end where it adds the default azure-pipelines.yml
Step 2: Click on the ellipse and click settings
Step 3: Specify the relative path to the azure-pipelines.yml in your directory, for example /MySolutionFolder/ProjectDir/azure-pipelines.yml
. Note it might not exist in the drop-down, that's fine. Click save and it should appear.
Upvotes: 2
Reputation: 1154
I couldn't find any official fix but this worked to me without having to remove any .yml files from any branch.
The URL that appears in the "Review" step looks like this:
https://dev.azure.com/{ORGANIZATION}/{PROJECT}/_apps/hub/ms.vss-build-web.ci-designer-hub?
sourceProvider=tfsgit&
telemetrySession={SESSION_ID}&
repositoryId={REPOSITORY_ID}&
repositoryName={REPOSITORY_NAME}&
branch={BRANCH_NAME}&
repositoryUrl={REPOSITORY_URL}&
sourceProviderComplete=true
Workaround: Replace branch name with a branch that has the .yml file you are looking for.
In my case ADO was putting 'Main' by default, and it didn't work until I changed it to 'Dev' which automatically redirected me to the 'Configure' tab.
Upvotes: 3
Reputation: 1286
I had an "azure-pipelines.yml" file in my repository root folder/all branches. It seems that once I removed this from all branches the configure option worked as expected.
Upvotes: 0