-
Bug
-
Resolution: Fixed
-
Major
-
Jenkins=2.32.3
Jobdsl=1.63
Folders=6.0.4
CredentialsPlugin=2.1.13
-
-
job-dsl-plugin 1.78, job-dsl-plugin 1.80
When using job-dsl-plugin to create a folder
folder(my_folder) {
displayname("my_folder_name")
}
If the folder exists with Credentials attached to it, they are lost on recreation 
. Is there anyway to wrap this in a conditional? if!(folder(my_folder) {blah..blah....}. I believe the desired behaviour here is to not blow away the credentials attached at the folder level.
- is related to
-
-
- Resolved
-
[JENKINS-44681] JobDSL Folder Creation Destroys Credentials
Bartlomiej Slowik
added a comment - Same issue here - its makes hard in our use case to manage auto-creation of folders and jobs. I would also favor an update/merge strategy instead of a hard override.
Bartlomiej Slowik
added a comment - Same issue here - its makes hard in our use case to manage auto-creation of folders and jobs. I would also favor an update/merge strategy instead of a hard override. The deletion of credentials is so unexpected. I just lost 95 folders with 100s of credentials due to this. I cannot express how frustrating this is.
I was able to recover most via the Job Config History plugin, but apparently "Secret File" credentials are magic and seem to be truly gone.
Gregory Paciga
added a comment - The suggestion in the first comment works, but only if not running in the groovy sandbox, or the user running the job is an admin (otherwise, every change to scripts needs to be approved by an admin).
Gregory Paciga
added a comment - The suggestion in the first comment works, but only if not running in the groovy sandbox, or the user running the job is an admin (otherwise, every change to scripts needs to be approved by an admin). I've been looking into this today, and have found a way to handle this within the plugin itself (via the IntelliJ debugger). I am going to be working on integrating this into the plugin itself, then will raise a PR on GitHub.
Graham McGregor
added a comment - The workaround suggested by daspilker above no longer works in sandbox mode with the latest version of the script-security plugin due to https://issues.jenkins.io/browse/JENKINS-63788
Graham McGregor
added a comment - The workaround suggested by daspilker above no longer works in sandbox mode with the latest version of the script-security plugin due to https://issues.jenkins.io/browse/JENKINS-63788 
Friedrich Clausen
added a comment - daspilker - any chance the above PR could get reviewed? 
i have a job that creates jobs in a tree, like:
foo/bar/baz/job-1
foo/bar/baz/job-2
etc
and i placed creds at the foo folder level, but every time i create another foo/bar/baz/job-x it blows away the creds at the foo folder!
not expected behavior and kind of a hassle to work around, i agree with folks on this thread that think that creds at existing folders should not be effected in this way...