[Enhacement] Include branch name when checking pipeline existence

[faisalriazz]

I am using azd version 1.11.0 to deploy Aspire Project using below mentioned link
https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment-github-actions?tabs=windows&pivots=azure-pipelines

Issue :
Project is already created and initiated using azd init, my current branch is dev.

• using this command azd pipeline config --provider azdo
• service connection is created automatically
• PAT is configured with required permissions.

First deployment from let us say Branch dev works fine and deployment started.
Second deployment from let us say Branch Stagging but different container app envoironment using azd init using the same PAT created in previous step and Azure service connection ( az connection) fails with error .
AZURE_ENV_NAME is invalid.

[rajeshkamal5050]

@vhvb1989 can you triage it?

[vhvb1989]

Hello @faisalriazz , can you please add more details about what you are doing? What do you mean by second deployment?
How are you trying to use different branches in your Azure DevOps?

When you run azd pipeline config, azd takes care of setting the CI/CD pipeline based on your current local git branch. Any other branches are not configured, only the one you are currently using. Azd sets ENV VARS for the pipeline that it creates.

Also, the documentation from https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment-github-actions?tabs=windows&pivots=azure-pipelines is a little outdated. You don't need to manually create the pipeline definition. You can just run azd pipeline config and azd will create it for you if it is missing.

[faisalriazz]

@vhvb1989 Thanks for your reply. Here are the details that i have done so far.

• In Branch main-cicd which i have created from main branch.
• I just run azd pipeline config and follow the procedure.
• Pipeline is working fine.

Now i repeated the same process but this time the Branch is main.

• Pipeline executed sucessfully.
  Issue is that both pipelines are trigerred for any change in one the branches either main or main-cicd.
• I have updated the triggers in azure-dev.yml file in both branches as

main-cicd branch

trigger:
  branches:
    include:
      - main-cicd
    exclude:
      - main

main branch

trigger:
  branches:
    include:
      - main
    exclude:
      - main-cicd

** Still both pipelines are triggered on change in any of the branch**

• I override the YML triggers in pipeline setting with the same as written in YML file.
• Now invidiual pipelines are trigerred individually but this is not understandable.
• Note I tried changing the name of the azure-dev.yml file in one branch and executed the pipeline but it failed in infrastructure provisioning task.
• Ultimately i have to revert the filename back to azure-dev.yml
• Would you please explain what is wrong with my procedure

[faisalriazz]

@rajeshkamal5050 @vhvb1989
Would you please update

[rajeshkamal5050]

@v-xuto can you repro the above steps and update? cc @vhvb1989

[vhvb1989]

@faisalriazz , thank you for the details.

Every time you run azd pipeline config, azd creates a definition for the pipeline and the branch you are currently using. The pipeline is the same, however. Azd currently does not support handling more than one pipeline for you.

I remember we built it this way to prevent creating a new pipeline after every azd pipeline config. Instead, we check if the pipeline already exist and update its definition. This is causing you an issue b/c you are re-running with a different branch.

I'll see if we can include the branch name while we check if the pipeline exists or not. In that case, you should see a different pipeline created for each branch.

Since this might take me some time, please be patient :)

[faisalriazz]

Thanks @vhvb1989 for the update, will be waiting anxiously for new version of azd :)

[v-weiyding]

@rajeshkamal5050 Based on the main and main-cicd branches, we can only create one pipeline instead of two separate pipelines. Moreover, within the same pipeline, when we make changes to the main and main-cicd branches and push them, only the corresponding branch's azure-dev.yml file will be executed.

[faisalriazz]

@v-weiyding Thanks for your input. Yes that can done but i want to keep it separate pipelines for the sake of simplicity.
I will be waiting for update azd version.