Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-65466

Permit valid job configurations with SSH credentials only

      Attempting to create a Bitbucket Server instance in any job type without HTTP credentials will fail due to an unresolved URL. This improvement would remove that requirement, and allow job creation and cloning only with SSH.

          [JENKINS-65466] Permit valid job configurations with SSH credentials only

          I believe this would require changes in Bitbucket Server as well.

          What would be the benefits of this feature?

          • Simpler credential management?
            If you don't want to maintain both SSH and HTTP credentials, then perhaps you can instead remove SSH and keep HTTP.
          • Encrypted communication between Jenkins and Bitbucket Server?
            Could be done with HTTPS instead, even with a private root.
          • Blocking access to most Bitbucket Server REST APIs, in case Jenkins is compromised?
            Could be done with a firewall and an HTTP proxy instead. That would also let you decide which APIs to allow through.

          Kalle Niemitalo added a comment - I believe this would require changes in Bitbucket Server as well. What would be the benefits of this feature? Simpler credential management? If you don't want to maintain both SSH and HTTP credentials, then perhaps you can instead remove SSH and keep HTTP. Encrypted communication between Jenkins and Bitbucket Server? Could be done with HTTPS instead, even with a private root. Blocking access to most Bitbucket Server REST APIs, in case Jenkins is compromised? Could be done with a firewall and an HTTP proxy instead. That would also let you decide which APIs to allow through.

            Unassigned Unassigned
            mhenschke_atlassian Martin Henschke
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: