-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
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.
- is duplicated by
-
JENKINS-66208 Allow Credentials for Build Auth to be personal access token or generic SSH access key
-
- Closed
-
- is related to
-
JENKINS-68423 Bitbucket Server Integration cannot checkout to the remote in a pipeline job
-
- Closed
-
I believe this would require changes in Bitbucket Server as well.
What would be the benefits of this feature?
If you don't want to maintain both SSH and HTTP credentials, then perhaps you can instead remove SSH and keep HTTP.
Could be done with HTTPS instead, even with a private root.
Could be done with a firewall and an HTTP proxy instead. That would also let you decide which APIs to allow through.