I'm having the error below when triggering my trigger pipeline, remembering that I've already set the application password and I'm using my username, not my email, if anyone can help me I will be grateful.
Error received: Account, repository or branch doesn't exist
I believe that you are referring to the 'Bitbucket trigger pipeline' pipe?
My suggestion is to check these 3 things:
1. Have you used the variable ACCOUNT in the definition of the pipe?
If the repo you want to trigger the pipeline for, is owned by a different workspace than the repo where you use the pipe atlassian/trigger-pipeline, you will need to specify the workspace-id in this variable. Otherwise, if both repos are owned by the same workspace, it is not necessary to use this variable.
2. Double check the name in the variable REPOSITORY.
If the repo name has capital letters, e.g. 'My_Repo', then you'll need to define the REPOSITORY variable using capital letters respectively.
Defining REPOSITORY: 'my_repo' will give an error if the repo is named 'My_Repo'. You will need to use REPOSITORY: 'My_Repo'
3. If you have used the variable BRANCH_NAME in the definition, double check that the branch exists in the repo you want to trigger the pipeline for, and that it has a bitbucket-pipelines.yml file.
Please feel free to let me know how it goes.
Good afternoon @Theodora Boudale ,
Thanks for the help, I'll try to explain better, my team has a web project that is in one repository, and I created some automated tests in another repository, the idea is that when there is a commit in the web project, the tests are automatically triggered in another repository.
follows link with images of the pipeline:
Thank you very much!
Thank you for the info! Looking at the configuration in the screenshot, I believe the issue is caused by the value in the variable REPOSITORY.
The value for this variable should be the repo name, instead of the URL.
If you want to trigger a pipeline in the repo e.g. https://bitbucket.org/my-company/company-repo/, then you can configure the pipe in the web project repository as follows:
- pipe: atlassian/trigger-pipeline:4.2.1
Could you give this a try and let me know if it works for you?
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events