Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
None
-
Jenkins 2.46.2
Pipeline: Shared Groovy Libraries 2.8
Folders: 6.0.2
git: 3.0.5-3.3.0
Description
In a folder, as standard user, when I try to add a global-scoped credential using the git implementation of the "modern SCM", I cannot select any credentials while it is possible to select the credentails when selecting git the Legacy SCM.
As administrator, it is possible to select the global-scope credential in both (Modern and Legacy) implementation.
The issue seems liked to the fact that when using the modern scm In jenkins.plugins.git.GitSCMSource.DescriptorImpl.doFillCredentialsIdItems(SCMSourceOwner, String, String), the context parameter is null.
When the legacy SCM is selected, in the hudson.plugins.git.UserRemoteConfig.DescriptorImpl.doFillCredentialsIdItems(Item, String, String) method, the project is not null and the global-scoped credentials are listed.
When I try the same process at the level of a job, both the modern and legacy SCM are able to list the credentials.
The issue could be liked to JENKINS-38048.
Attachments
Issue Links
- is duplicated by
-
JENKINS-45844 Cannot bind folder credentials to pipeline shared library using Modern SCM option
-
- Closed
-
Code changed in jenkins
User: Andy Neebel
Path:
src/main/java/jenkins/scm/impl/subversion/SubversionSCMSource.java
http://jenkins-ci.org/commit/subversion-plugin/c056e9af67458d94106f617ab97e2579b5f27b92
Log:
JENKINS-49624Fix selecting credentials for Pipeline Libraries using Modern SCM (#206)Comes from
JENKINS-44271, applying fix for git-plugin to subversion-plugin