-
Bug
-
Resolution: Fixed
-
Minor
-
None
getCredentials(Class,Item,Authentication,List) has not been overridden so the default behaviour of redirecting to Item.getParent() means that the folder's own credentials are not available to the folder itself.
This was an oversight in the implementation of the CredentialsProvider contract for folders.
- is blocking
-
JENKINS-36066 Credentials visibility
-
- Closed
-
- is related to
-
JENKINS-36196 Organization folder and multi-branch projects should support folder-level credentials
-
- Closed
-
- links to
amuniz stephenconnolly did this fix the issue that the Add dropdown in, say, http://jenkins/job/some-multibranch/pipeline-syntax/ with, say, the git step selected, offered only Jenkins and not the (computed) folder itself?