branch permissions and SSH access keys for system use

[Stephane Genin]

Hello,

We have configured an access for Jenkins to automatically do some actions (such as branch merges), and we followed this documentation to store the related SSH access keys : https://confluence.atlassian.com/bitbucketserver0412/ssh-access-keys-for-system-use-869179319.html. This allows us not to create an account for Jenkins.

We have branch permissions to control which users can do merges on some branches.

We would like Jenkins to be able to perform some of these restricted actions. 

Is it feasible? Or shall we create a technical user for Jenkins anyway?

Thanks

[anthony.slabinck@liantis.be]

Hi Stephane,

I added an SSH key under team settings. It seems to be impossible to give that SSH key write access on a repository. 

Creating a specific user for Jenkins is also something I was thinking about, but this would mean you have to pay for that user.

Did you choose this solution or are there beter alternatives in 2019?

Thanks in advance.