I would like to grant my developers permission to edit bitbucket pipelines, without simultaneously giving them the permission to administer access permissions for other users and user groups of a repository. Is this possible?
So far, the only way I found to grant users the right to edit bitbucket pipelines, is to give them admin rights, which unfortunately includes the permission to invite new users to a repository, as well as changing to access permissions of groups that have access to the respective repository. Is there a way to separate the two?
Thanks!
Which part of Pipelines do you want them to be able to edit? The bitbucket-pipelines.yml file controls most of the active workflow, and it's a regular file within the repository - so any user with write access can modify it. They'd only need admin rights to change environment variables or SSH keys; to set up Pipes or other integrations; or to enable or disable Pipelines altogether.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.