we use the branch name as base for our docker tags. Unfortunately the custom pipelines get checked out as 'detached HEAD' and thus branch is always set to 'HEAD'.
Nown there is a environment variable which i wanted to use but this is not available for custom pipelines but only for branch pipelines. See this help article.
Question: How can i get my source branch name for my build script?
Hi Sebastian, if you trigger a manual pipeline for a commit, Pipelines can't tell which branch to run it with (a commit exist on multiple branches)
However, if you trigger the custom pipeline from the branches page, you will get the $BITBUCKET_BRANCH variable
See the screenshot for https://bitbucket.org/site/master/issues/14002/running-custom-pipeline-for-a-branch-does
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot