You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi I'm currently having some trouble setting up a pipeline when I'm merging a feature branche in my develop branch and generating a Changelog.
Current situation
Wished situation
Right now my pipeline is being stuck in a loop since I'm pushing my generate changelog to develop after the merge.
Current bitbucket-pipelines.yml
pipelines:
branches:
develop:
- step:
caches:
- node
script: # Modify the commands below to build your repository
- git config user.email "my_email.com"
- git config user.name "my_name"
- npm install
- npm run release
- git push --follow-tags origin develop
I hope you guys can help me out!
This feature is yet to be implemented by atlassian dev team. I have added reasons why this feature would be ideal in two (of many more) scenarios to the aforementioned feature request:
https://bitbucket.org/site/master/issues/13867/run-pipeline-on-the-result-of-the-pull
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @[deleted],
There's a feature request open at https://bitbucket.org/site/master/issues/13867/run-pipeline-on-the-result-of-the-pull that I would love to get your feedback on.
We use bitbucket site/master issues to track customer requests and feedback on improvements we can make to Pipelines.
Thanks,
Seb
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Was there an update on this issue?
I was asked to execute a task upon a merge into master, and not on a master branch build.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For future reference, you can disable triggering the pipeline by committing with "[skip ci]" in the commit message - see FAQ about this.
What I would do in the requested scenario is to actually implement CHANGELOG in the PR itself to be able to review it *before* merging to develop happens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.