-
Bug
-
Resolution: Fixed
-
Minor
-
None
The credentials are not using the API endpoint to enabled selection from credential domains.
This makes it impossible to keep say GitHub Enterprise credentials in a credentials domain scoped to the enterprise server's hostname.
Also, when there is more than one endpoint defined in the system, the endpoint is hidden in an Advanced box. When there are multiple endpoints the user should be able to select the api endpoint without having to expand the advanced box and find the hidden setting
- is blocked by
-
JENKINS-41904 NPE when selecting a scan credential for GitHub SCM on Pipeline Libraries
-
- Resolved
-
- links to
Code changed in jenkins
User: Stephen Connolly
Path:
src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java
src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator.java
src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java
src/main/resources/org/jenkinsci/plugins/github_branch_source/GitHubSCMNavigator/config.jelly
src/main/resources/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource/config-detail.jelly
http://jenkins-ci.org/commit/github-branch-source-plugin/b7788c606b43f29fc91d277de81a67a65abe39d4
Log:
[FIXED JENKINS-40451] Respect the API endpoint for credentials domains