The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Trigger options I have looked at are:
- `branches` will run automatically on a commit to a branch
- `pull-requests` in my testing will run when a pull request is created or merged
I would like a trigger that runs on each commit to a branch that is currently part of a pull request.
I am considering using the branches trigger for all branches and writing a custom pipe to check the Bitbucket API to get any related PRs for the commit. The downside being that it would require a pipeline run for every commit to any branch and I am not sure what I would do in the case no PR was found. I guess in that instance I could fail the build but that is not an ideal outcome to have a bunch of failed builds in my pipeline history.
Hello @Wayne Pichotta ,
Welcome to Atlassian Community!
When you use the pull-requests trigger, it will trigger the pipeline in the Pull-Request creation, as well as in every push to the source branch of the pull request.
Let's take the below YML file as an example:
pipelines:
pull-requests:
'**': #this runs as default for any branch not elsewhere defined
- step:
script:
- echo "Runs for any branch not defined below"
feature/*: #any branch with a feature prefix
- step:
script:
- echo "Runs for any branch that starts with feature"
Supposing that I have created a branch called feature/1 from master. When I create a Pull Request from feature/1 to master, the pull request pipeline feature/* will be triggered. While the Pull request is open, every subsequent commit to the source branch of the PR (in this case feature/1) will also trigger the pipeline feature/*.
You can use something similar to the above in your yml to get the pipeline to trigger in every commit to a branch that is the source of a pull request.
Hope that helps! Let me know in case you have any questions.
Thank you, @Wayne Pichotta .
Kind regards,
Patrik S
@Patrik S wow that is embarrassing. It does exactly what I was asking for. I thought it was not acting that way in my testing last week. Thanks for your patience and taking the time to answer. This is great.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Wayne Pichotta ,
No worries at all :) I'm glad to have been of some help.
Thank you, @Wayne Pichotta !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.