"Account, repository or branch doesn't exist" error when using "atlassian/trigger-pipeline" pipe
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
When using older versions (< 5.7.0) of the atlassian/trigger-pipeline pipe - you may encounter errors when attempting to execute your build
Environment
Bitbucket Cloud Pipelines
Diagnosis
Some variant of the following error message is encountered when executing your build, causing it to fail:
"Account, repository or branch doesn't exist"Cause
The incorrect variable definition has been used
The branch or repository has been entered incorrectly or does not exist
Solution
When attempting to use a pipe, you should always refer to its relevant pipe documentation to determine the correct variables to use in your YAML configuration
The newer version of the pipe atlassian/trigger-pipeline:5.7.0 was updated so that "BRANCH_NAME" has been changed to "REF_NAME".
It is recommended to use the latest version of the pipe, considering also the app password deprecation. You can find the latest version of the pipe in the pipe's repo.
Example (with version 5.10.1):
script:
- pipe: atlassian/trigger-pipeline:5.10.1
variables:
REPOSITORY: '<string>'
# ATLASSIAN_ACCOUNT_EMAIL: '<string>' # Optional
# ATLASSIAN_API_TOKEN: '<string>' # Optional
# BITBUCKET_ACCESS_TOKEN: '<string>' # Optional
# ACCOUNT: '<string>' # Optional
# REF_TYPE: '<string>' # Optional
# REF_NAME: '<string>' # Optional
# COMMIT: '<string>' # Optional
# CUSTOM_PIPELINE_NAME: '<string>' # Optional
# PIPELINE_VARIABLES: '<json>' # Optional
# WAIT: '<boolean>' # Optional
# WAIT_MAX_TIMEOUT: '<integer>' # Optional
# REQUEST_READ_TIMEOUT: '<integer>' # Optional
# MAX_RETRIES_ON_FAILURE: '<integer>' # Optional
# DEBUG: '<boolean>' # OptionalIf you have correctly defined the pipe in your YAML configuration based on the above YAML snippet - but you are still encountering issues, please ensure that you have entered the branch/repository name correctly.
If the above instructions do not assist in resolving the issue, please raise a support ticketor raise a community support ticket for further assistance with this.
Was this helpful?