Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple pipelines with the same name #28

Open
mbpolan opened this issue Apr 21, 2021 · 0 comments
Open

Multiple pipelines with the same name #28

mbpolan opened this issue Apr 21, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@mbpolan
Copy link

mbpolan commented Apr 21, 2021

I have a GitHub Action that should trigger an Azure DevOps pipeline. In my project, I have multiple pipelines that have the same name, but are grouped under different folders by convention. For example:

+ my-app-1
  - deploy
+ my-app-2
  - deploy

In the above, my-app-1 and my-app-2 are folders corresponding to different repositories, and our standards are to have a deploy pipeline for each repository. I would like to trigger specific deploy pipelines using a GitHub Action.

- name: Azure Pipelines Action
  uses: Azure/pipelines@v1
  with:
    azure-devops-project-url: https://dev.azure.com/organization/project
    azure-pipeline-name: 'deploy'       # this is in question
    azure-devops-token: ${{ secrets.AZURE_DEVOPS_TOKEN }}

How would I configure the action to trigger the my-app-1/deploy pipeline specifically?

In the above snippet, if I specify deploy by itself, I get an error:
More than 1 Pipeline named "deploy" found in project "project"

If I try to prefix this with either my-app-1/deploy or my-app-1\deploy, I get a different error:
Failed request: (401)

The only way I'm able to get this to work is if I give each pipeline a unique name, but I'd prefer not to have to break my existing conventions to do this.

@Josh-01 Josh-01 added enhancement New feature or request P1 Some scenario broken but workaround exists question Further information is requested and removed question Further information is requested P1 Some scenario broken but workaround exists labels Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants