Jenkins credential changes every time redeploy and No longer useful
See original GitHub issueYour checklist for this issue
🚨 Please review the guidelines for contributing to this repository.
-
Jenkins version
-
[x ] Plugin version
-
[x ] OS
Description
jenkins version : Jenkins ver. 2.225 Plugin version : 1.36
Steps:
- Configured GitHub credentials from jenkins UI
- Copy content from cofig as code yaml file
- Added connect to jenkins helm chart yaml
- Redeploy jenkins
Issue: Credetial chages and no usefull anymore. deleted and added again from UI and started working. noticed original hash for password got changed
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (10 by maintainers)
Top Results From Across the Web
Using credentials - Jenkins
Credentials can be added to Jenkins by any Jenkins user who has the Credentials > Create permission (set through Matrix-based security). These permissions...
Read more >How do I fix Jenkins github app credentials issue?
I can go to each job and when I select 'validate', the github app credentials are validated fine. I created a dummy job...
Read more >Breaking the Jenkins Monolith - Medium
Configuration changes should be traceable over time and teams should have the ability to redeploy or rollback their instance at the click of...
Read more >How To Create a Jenkins Build Job to Automate Web ...
But if you regularly make changes to your project, will you have to redeploy each time manually? Why not set up build triggers?...
Read more >Create a Continuous Deployment Pipeline with Jenkins & Java
With this Couchbase guide, learn how to use Jenkins for ... Java backend and Angular frontend every time a change was detected on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I would consider this works as intended.
LDAPS is working for me, it is base64 encoded kubernetes secret, the secret name is the same as the key inside. kubectl get secrets -n jenkins ldappsd.data.password -o yaml apiVersion: v1 data: ldappsd.data.password: <base64 encoded> kind: Secret metadata: When the secret is mounted, use the mount path managerPasswordSecret: “${readFile:/<mount path>/ldappsd.data.password}”