nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pipelines permissions and conditions

Luc Debliquis

Hello,

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 ?

Thanks,

Luc

Accepted answers

Philip Hodder

Hello,

Bitbucket Pipelines now provides the ability to place restrictions on triggering Deployment Steps. Right now you can restrict them to only being triggered by repository administrators, and/or on a specific branch.

For example, you could set a production deployment to only be able to be triggered by a repository admin off the 'master' branch.

You can configure them in your repository settings, in the Deployments tab.

Have a look here for more information: https://bitbucket.org/blog/deployment-permissions-now-available-in-bitbucket-pipelines

Thanks,

Phil

All comments

Luc Debliquis

someone ??

Md Mehrab Alam

@Luc Debliquis u got any solution

Luc Debliquis

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/pipelines-validate-branch.sh $BITBUCKET_BRANCH demo

script:

#!/bin/bash
# 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" ];
then 
 echo "Deployment on master is not allowed from the branch $1 (only from master)" 
exit 1
fi 
# can deploy dev and master on demo
if [ $2 = "demo" -a $1 != "master" -a $1 != "dev" ];
then 
 echo "Deployment on demo is not allowed from the branch $1 (only from dev and master)" 
 exit 1
fi 
# other manual deploy will fail
if [ $1 != "dev" -a $1 != "master" ];
then 
 echo "Manual deployment is not possible from this branch (only from dev and master)" 
 exit 1
fi

Daniel Whatmuff

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

Anil Kumar_doanrz

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

pipelines: 
     custom: 
        stage-search-app: 
          - step: caches: - node 
               script: 
                    - if [[ $BITBUCKET_BRANCH != develop ]]; then exit 1 ; fi