Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Pipeline trigger run fails

Steven Delrue May 10, 2022

When running a trigger in bitbucket pipelines, I get this error :

 Error: {"error": {"message": "Bad request", "detail": "bitbucket-pipelines.yml not found.", "data": {"key": "result-service.pipeline.yml-not-found", "arguments": {}}}}

The repo which should trigger the pipeline is a private team repo, but I should have all the rights (I can read & write to the repo)

This is bitbucket-pipelines.yml: 

pipelines:
  branches:
    development:
      - step:
          name: Trigger Boilerplate & Xperify Build (development)
          script:
            - pipe: atlassian/trigger-pipeline:5.0.0
              variables:
                BITBUCKET_USERNAME: $TRIGGER_USERNAME
                BITBUCKET_APP_PASSWORD: $TRIGGER_PASSWORD
                REPOSITORY: oculariumfrontendboilerplate
                REF_TYPE: 'branch'
                REF_NAME: 'development'
            - pipe: atlassian/trigger-pipeline:5.0.0
              variables:
                BITBUCKET_USERNAME: $TRIGGER_USERNAME
                BITBUCKET_APP_PASSWORD: $TRIGGER_PASSWORD
                REPOSITORY: ocularium-frontend-xperify
                REF_TYPE: 'branch'
                REF_NAME: 'development'

The app password I generated has the correct permissions set

2 answers

1 accepted

1 vote
Answer accepted
Mark C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 11, 2022

Hi @Steven Delrue

Thank you for reaching out to the community.

Based on the error message, it seems there's no recognized file (bitbucket-pipelines.yml) in the "development" branch of your private repository.

Would it be possible for you to check if the file (bitbucket-pipelines.yml) exists in the private repository "development" branch?
You can use this link to check it, just change it with your workspace ID and repository name:

https://bitbucket.org/workspace_id/repo_name/src/development/

Let me know how it goes.

Regards,
Mark C

Steven Delrue May 30, 2022

It turns out that the problem was that the bitbucket-pipelines.yml file was present in the target repository (the repo which is getting triggered), but it didn't contain a pipeline matching the development branch.

Tiago Emanuel Felix Mateus May 26, 2023

@Steven Delrue sorry, Im new at this, could you clarify what you mean with "a pipeline matching the development branch"?

Im having the exact same issue.

0 votes
lissyaka May 13, 2022

Hi @Steven Delrue .

Also please check that you enabled pipeline support in your triggered repository.

Cheers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events