We allow for branch create by pushing a branch. This triggers a build in Jenkins via the Stash Webhook to Jenkins plugin. This is not a bad as such...
But, when the user creates a PR for the pushed branch, a new build is started for the same branch. This is not a good thing since this consumes resources in our CI.
Is there something I have missed in config or is this simply the way it works?
Answering my own question since I got it to work the way I want. Which is that a build is ONLY started when a PR is created.
Branch specifier: pr/*
check the box for "Omit branch name".
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot