The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

trigger-pipeline failed

Safder Qasim
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2021

Here is my Pipeline Step 

Screenshot from 2021-02-03 18-27-03.png

I am getting following error while triggering another pipeline of the different repository with in the same workspace. I do have bitbucket-pipelines.yml file in my 2nd repo which I needs to trigger from my source pipeline. Here is the error which I am getting:

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

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Safder Qasim
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 3, 2021

I have found that bitbucket api is unable to connect with my repo and given 400 http status code. Though I can open my repo in the browser by adding MyWorkspaceID/qa-domain-all.

DEBUG: "POST /2.0/repositories/MyWorkspaceID/qa-domain-all/pipelines/ HTTP/1.1" 400 160

TAGS
AUG Leaders

Atlassian Community Events