-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins 2.452.1
Found issue on credentials plugin side. Credentials became unusable after updating it's value.
Steps to reproduce
1. Create new credentials, for gitlab access token (just an example). Use it in a pipeline, Should work.
2. Generate a new token on gitlab side.
3. Update existing credentials with new token and try to use it in pipeline. Will not work and return "Unauthorized" from gitlab side.
Gitlab here is just an example, the same behavior we can see with any credentials.
Jenkins version: 2.452.1
Credentials plugin version: 1371.vfee6b_095f0a_3
Is it a known bug?
I'm unable to duplicate the bug. I installed Jenkins 2.452.1 and credentials plugin 1371.x, configured a GitLab organization folder and a GitLab muultibranch Pipeline with working credentials, scanned the organization folder and the multibranch Pipeline, then created a new GitLab access token, updated the values in the Jenkins credentials, and confirmed that the new credentials worked as expected in both cases.
Can you provide more details so that others can duplicate the issue?