The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can I prevent bitbucket-pipelines.yml to be modified by developers?

Victor Acin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 9, 2020

Hello,

We have set up our bitbucket-pipelines.yml file, pushed to the repo and it's working. We have read a lot about this configuration but we don't find anything about preventing developers, or just allowing some of them, to modify this file.

This is very important for us, because one developer with access to the repo can wilfully make the server crash if he modifies the source code and modify the pipelines so that Bitbucket does not run the tests and create the build properly.

I think there should exist something but we don't find it.

 

Many thanks in advance,

Victor.

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

1 vote
raschidjfr
Contributor
March 18, 2020

There's currently a feature request for this: BCLOUD-19457.

You can vote for it.

Patrick Wickham
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 8, 2021

^ Everyone please vote for this -- this is a massive oversight that needs to be fixed

1 vote
Lenin Raj
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 11, 2020

Hi @Victor Acin

 

I am afraid this isn't possible. However to prevent someone from modifying the bitbucket-pipelines.yml file, you can use Branch Permissions, assuming your build/deployment runs from master branch.

 

This will prevent anyone working on the repository to merge anything without approval.

raschidjfr
Contributor
March 18, 2020

I just want to add that with this approach you would need a Premium Membership to be able to restrict access to certain Deployments (and its variables) ton only selected branches.

But that won't prevent anyone from being able to use those variables in a malicious script in the yaml file, unless the repo admin keeps an eye on what is being modified and merged... which is the opposite of automating 🤦🏻‍♂️

I guess we need to start a feature request.

TAGS
AUG Leaders

Atlassian Community Events