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

Pipelines permissions and conditions



First, congratz to the team for such a good feature, very quick and easy to implement a full ci/cd cycle with pipelines.


2 questions:

1. I want to add a manual (custom) pipeline run in the yml file.
How can i restrict permissions on who is allowed to run this custom build ?


2. I want this build to be runable only on the master branch, how can i limit this ?
I am thinking of a custom step, and checking the $BITBUCKET_BRANCH in the yml..
But there might be an easier way ?






5 answers

Ability to restrict permissions for manual/custom pipelines would be a massive help for us..

someone ??

We can do something like this . We can manually force pipeline to fail.


step: caches: - node
if [[ $BITBUCKET_BRANCH != develop ]]; then exit 1 ; fi

Good suggestion.

But the problem is that every developer would be able to modify it on a feature branch and thus trigger the build from this branch

You could use Pull-Requests from feature branches, and then code reviews. But yeah, it's not ideal.

@Luc Debliquis u got any solution

For permissions, no. No answer at all.. great.

For branch selection, i added a step with a custom bash script that validates the branch name (sent as parameter by pipelines to the script)

- sh deploy/ $BITBUCKET_BRANCH demo




# expects the source branch as first parameter, and the target environment as 2nd
echo "source branch: " $1
echo "target environment: " $2
# can only deploy master on master
if [ $2 = "master" -a $1 != "master" ];
"Deployment on master is not allowed from the branch $1 (only from master)"
exit 1
# can deploy dev and master on demo
if [ $2 = "demo" -a $1 != "master" -a $1 != "dev" ];
"Deployment on demo is not allowed from the branch $1 (only from dev and master)"
exit 1
# other manual deploy will fail
if [ $1 != "dev" -a $1 != "master" ];
"Manual deployment is not possible from this branch (only from dev and master)"
exit 1

+1 for access control on custom pipelines

+1 for branch-dependent or branch-restricted custom pipelines

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published Mar 14, 2019 in Bitbucket Pipelines

Building a Bitbucket Pipe as a casual coder :  #!/bin/bash source "$(dirname "$0")/" enable_debug extra_args="" if [[ "${DEBUG}" == "true" ]]; then extra_args="--verbose" fi # mandatory variables R...

1,042 views 1 16
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you