Git Blue Ocean plugin creates ssh key

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I'm running Jenkins within a docker container.

      The actual problem I'm having is that the blueocean-git-pipeline plugin in version 1.3.0 does not allow to select credentials when using an SSH Git link. As shown in image1

      Before that in version 1.2.3 it was possible to select credentials as shown in image2, which is now only possible for http(s) Git links.

      The benefit with the configuration as shown in image2 is that I only need one ssh key for jenkins and gitlab and don't potentially need a new key for every user.

      For me this is a bug for two reasons:

      1. I start my Jenkins docker container with all credentials configured, so there's no need to add new credentials and to avoid to add different ssh keys to our internal GitLab.
      2. Everytime I restart the docker container it looks like a new key is generated, so I would have to got to GitLab and remove the "old" key and add the new key.

        1. image1.png
          74 kB
          Stephan Huber
        2. image2.png
          35 kB
          Stephan Huber

            Assignee:
            Unassigned
            Reporter:
            Stephan Huber
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: