Missing Credentials in Dropdown for Jenkins Build Configuration
Hello!
Recently I updated my Jenkins installation including all of the plugins. One of them must have brought somewhat breaking changes because when I tried to create a new build configuration for a new old project of mine, I could not select the proper credentials in the dropdown. I only had the option to add new ones even though I had added the corresponding credentials in the global scope (as per usual), so they must have been visible across the entire Jenkins instance. None of them were showing up. And even when I tried adding new ones through the build configuration page, they ended up not being active / selected either.
When I went back to check with an existing build configuration I had configured over a year before, I could confirm the same behavior. For build parameters the credentials dropdowns were empty and for the VCS credentials it said
Cannot find any credentials with id <ID>
I spent a couple of hours looking for solutions and I did find some cases that popped up around 1 or 2 years ago, but nothing that fit this exact scenario. My suspicion was that this might be a bug, so I tried rolling back the SSH credentials and credentials plugins to the previous versions, but that did not fix anything.
I decided to wait for a week in the hopes of potential bug fix releases to come out for either some of the plugins or Jenkins itself, but a week later in spite of a couple of updates here and there, nothing about the problem had changed.
And then I found a comment in the discussion thread of a GitHub issue of the "GitHub Pull Request Builder Plugin" (which I am not even using). In it, the following solution was proposed:
- Navigate to "Jenkins" (main menu) => "Manage Jenkins" => "Configure Global Security"
- Go to the "Access Controls for Builds" section
- Under "Project default Build Authorization" check if the "Strategy" is set to "Run as anonymous" (which was the case for me)
- If yes, try changing it to "Run as User who Triggered Build" (it might also work with another setting if that suits you better)
- Save and reload the build configuration settings
That was it! The credentials showed up again and I could execute the build successfully.
I know this seems to be a niche problem and there might only be a handful of people that have encountered the same issue, but I hope it was helpful nonetheless.
Thank you for reading!
Calendar
M | T | W | T | F | S | S |
---|---|---|---|---|---|---|
1 | ||||||
2 | 3 | 4 | 5 | 6 | 7 | 8 |
9 | 10 | 11 | 12 | 13 | 14 | 15 |
16 | 17 | 18 | 19 | 20 | 21 | 22 |
23 | 24 | 25 | 26 | 27 | 28 | 29 |
30 | 31 |
Recent Posts
- Windows Defender Firewall Inbound Rule for ICMPv6
- (Re)Setting Hyper-V Virtual Machine Client Zoom Level
- Uploading a Snapshot to a Fresh Home Assistant OS Instance
- Fix GNOME GUI Login After Upgrade to Debian 10 Buster (VirtualBox VM)
- Missing Credentials in Dropdown for Jenkins Build Configuration
Top Posts & Pages
- Fixing Low Stereo Out Sound Volume For the Yamaha MG12XU / MG16XU / MG20XU Audio Mixer
- Memory Leaks / Problems with Long-Running Symfony / Doctrine Console Applications
- (Re)Setting Hyper-V Virtual Machine Client Zoom Level
- Missing Credentials in Dropdown for Jenkins Build Configuration
Subscribe to Blog via E-mail
Categories
Archives
- May 2022
- April 2022
- May 2020
- July 2019
- June 2019
- October 2018
- May 2018
- January 2018
- December 2017
- October 2017
- September 2017
- August 2017
- March 2017
- February 2017
- January 2017
- December 2016
- June 2015
- November 2014
- December 2013
- July 2013
- May 2012
- April 2012
- March 2012
- January 2012
- June 2011
- May 2011
- June 2010
- April 2010
- January 2010
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009