-
Bug
-
Resolution: Unresolved
-
Major
-
None
Scriptler-plugin Jcasc permissions for role based security stopped working after release 3.5.
The following jcasc yaml file works for version 3.4
jenkins: authorizationStrategy: roleBased: roles: global: - assignments: - <some user> name: "admin" pattern: ".*" permissions: - "Scriptler/Configure" - "Scriptler/RunScripts" .....
After release 3.5 Jenkins throws an internal server error on start up as it cannot map the Scriptler permissions. Going through the commits for the 3.5 release I found that the permisions are moved to a dedicated file - https://github.com/jenkinsci/scriptler-plugin/commit/be98485e8688ead6f1a6928043d82fc71a390e00
[JENKINS-68526] Scriptler-plugin Jcasc permissions for role based security stopped working after release 3.5
Description |
Original:
Scriptler-plugin Jcasc permissions for role based security stopped working after release 3.5.
The following jcasc yaml file works for version 3.4 {code:java} jenkins: authorizationStrategy: roleBased: roles: global: - assignments: - <some user> name: "admin" pattern: ".*" permissions: - "Scriptler/Configure" - "Scriptler/RunScripts" ..... {code} After release 3.5 Jenkins throws 500 as it cannot map the Scriptler permissions. Going through the commits for the 3.5 release I found that the permisions are moved to a dedicated file - [https://github.com/jenkinsci/scriptler-plugin/commit/be98485e8688ead6f1a6928043d82fc71a390e00] |
New:
Scriptler-plugin Jcasc permissions for role based security stopped working after release 3.5.
The following jcasc yaml file works for version 3.4 {code:java} jenkins: authorizationStrategy: roleBased: roles: global: - assignments: - <some user> name: "admin" pattern: ".*" permissions: - "Scriptler/Configure" - "Scriptler/RunScripts" ..... {code} After release 3.5 Jenkins throws an internal server error on start up as it cannot map the Scriptler permissions. Going through the commits for the 3.5 release I found that the permisions are moved to a dedicated file - [https://github.com/jenkinsci/scriptler-plugin/commit/be98485e8688ead6f1a6928043d82fc71a390e00] |
Experiencing the same issue with Scriptler 3.5
Reproduced locally using:
This problem appears during Jenkins startup:
java.lang.IllegalStateException: Cannot resolve permission for ID: Scriptler/Configure
Stack trace:
A workaround to this is to comment out Scriptler permissions in yaml, start Jenkins, and then load the configuration from disk. This could mean that casc plugin is loading permissions before Scriptler plugin is initialized.
Similar issue could be: https://issues.jenkins.io/browse/JENKINS-66271