I see for access to the repository, we have read, write and admin permissions. As I understand it, since Pipelines is code in the repository, permissions to change its configuration is based on the developer permissions for the repository.
I notice there is a premium feature, which you can then block certain branches to be only deployed by admin. I am assuming then this is the repository admin permission.
This seams a bit lacking to me, coming from Bamboo and being use to the plethora of permissions there. I feel there are use cases where I would like part of the development team to be able to execute a deployment, but not be an admin over the whole repository.
Is it just me or is Bitbucket Pipelines lacking a bit for permissions in this regard? I haven't looked at Github or Gitlab to see if their permissions are similar or more robust.
Thanks.
Hi Curtis,
Thank you for reaching out. We have a feature request for the ability to add non-admin user groups in deployment permissions:
You can add your vote to that feature request (by selecting the Vote for this issue link) to express your interest. You are more than welcome to leave any feedback, and you can also add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.
Implementation of features is done as per our policy here and any updates will be posted in the feature request.
Kind regards,
Theodora
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.