Joseph Petersen
Joseph Petersen
> Dear bot, reopen please. Okay 😅
This is not really a JCasC feature request. This is a script-security-plugin: https://github.com/jenkinsci/script-security-plugin Which uses jira issues: http://issues.jenkins-ci.org/
Unless what your asking is some hashing logic much like base64 logic in #1408
https://github.com/jenkinsci/script-security-plugin would need a `DataBoundSetter` for `approvedScriptHashes` which is currently not implemented. Only a `DataBoundSetter` is available for approvedSignatures: https://github.com/jenkinsci/script-security-plugin/blob/3b77f808a71620a526a59a2e625d289b4c249234/src/main/java/org/jenkinsci/plugins/scriptsecurity/scripts/ScriptApproval.java#L664-L681
@codepitbull please do share your workaround with JCasC groovy plugin
I like this idea of separating them out for the concern for developers
@ndeloof agreed though the basis for splitting is to allow the configurator API to stay on 2.60.3 while JCasC plugin can benefit from newer core releases. One of the things...
@timja hopefully, if we split the right way that can minimal core stay on 2.60.3? We also discussed moving our test methods to the jenkins test harness.
Seems like a odd use case. The same can be achieved by using shared libraries.
depending how you write your seed job you can use a pipeline job for your seed.