Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Bitbucket cloud api run pullrequest pipeline build

Docs missing example of how to run pipeline for a pull request.

Something like:

curl -X POST -s -H "Authorization: Bearer $access_token" -H "Content-Type: application/json" "https://api.bitbucket.org/2.0/repositories/$USERNAME/$REPOSITORY/pipelines/" -d '{ "target": { "type": "pipeline_pullrequest_target", "source": "feature/foo", "destination": "master" } }'

Returning:

{"code": 500, "message": "There was an error processing your request. It has been logged (ID 881d1e9798f2e21f)."}

 wondering if anyone were able to run pipeline for a pullrequest

1 answer

0 votes
Peter Plewa Atlassian Team Sep 02, 2019

Hi @Alexandr Marchenko

You can definitely run a pipeline for pull request. Those get triggered automatically on any existing Pull Request updates, but if you rerun any of existing one you can see what the expected parameters are. It doesn't seem to be documented so you'd have to try few combinations to find required parameters.

I've managed to trigger new PR pipeline with similar structure:

{
"target": {
"type": "pipeline_pullrequest_target",
"source": {BRANCH},
"destination": "master",
"destination_commit": {
...
},
"pullrequest": {
...
},
"selector": {
"type": "pull-requests",
"pattern": "**"
},
"commit": {
...
}
}
}

Thanks,
Peter

What do you mean by "but if you rerun any of existing one you can see what the expected parameters are"? How to see them?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

538 views 6 4
Read article

Community Events

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

Events near you