Unable to use existing SSH key when creating new pipeline

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

XMLWordPrintable

      In previous versions of Blue Ocean, when I created a pipeline and selected "Git" as the type, I could select existing SSH keys configured in Jenkins. Now it forces me to add a new key to my git server when creating a new pipeline.

      I would like to be able to use an existing key, to avoid additional administrative overhead. I'm assuming this is a bug? Not sure as I don't see any mention of changes to the flow in the plugin page (but I could have missed it).

      I'm using Blue Ocean 1.3.0.

      The functionality was working as expected (allowing use of existing keys) as of 1.1.0 and I think was working in 1.2.0 also (but not 100% sure).

            Assignee:
            Unassigned
            Reporter:
            Jordan Jennings
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: