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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,706
Community Members
 
Community Events
176
Community Groups

Pipeline trigger run fails

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 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

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.

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

Atlassian Community Events