Details
-
Suggestion
-
Resolution: Won't Fix
Description
I have my own Jenkins server and I want to do "git push" to my Bitbucket repo using ssh keys. I don't want to use my personal ssh key though because I have multiple repos and multiple Jenkins jobs, projects and whatnot.
when I go to Bitbucket web site to create an ssh key that would be specific to a repo, I see it requires Pipelines to be enabled, which means adding a pipeline yaml file and so on. I don't want to use Pipelines for this project.
are you planning to support ssh keys with access control per repository?
I want to create several ssh keys and define permissions per repo and per Jenkins job type, e.g. "ssh key for REPO x with PUSH permission"