- When I am creating a Freestyle or Maven Job, and I select the Git SCM configuration section, the credentials dropdown is empty. If I check other SCM section like SVN, I can load the credentials correctly.
- CloudBees CI (CloudBees Core).
- CloudBees CI (CloudBees Core) on modern cloud platforms - Managed controller
- CloudBees CI (CloudBees Core) on traditional platforms - Client controller
- CloudBees Jenkins Enterprise
- CloudBees Jenkins Enterprise - Managed controller
- CloudBees Jenkins Team
- CloudBees Jenkins Platform - Client controller
- Jenkins LTS
- Git Plugin
- Authorize Project Plugin
This is a known issue affecting different Jenkins versions as well as Git Plugin versions. And it happens in environments where you have installed the Authorize Project Plugin and you configure it as shown below:
Manage Jenkins-> Configure Global Security-> Project default build Authorization section:
I have selected anonymous as the user under which I will run the build
- I have selected to run builds as a specific user:
In order to get access to the credentials list, you should enable any of the other authorization types at the Configure Global Security level: SYSTEM or the user who triggered the build.
Once that you change the settings to the ones mentioned, you will get the credentials list back in your jobs.
- Git Plugin v3.8.0
- Authorize Project Plugin v1.3.0
- CloudBees CI (CloudBees Core) on traditional platforms - Client controller v126.96.36.199.1