New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support of dynamically-modifyable system properties in YAML #81
Comments
Can you please provide a link to this mechanism ? Never heard about his |
I think what @oleg-nenashev meant is to control system properties that Jenkins reads. So instead of this in a docker image
It could be something like this: systemProperties:
- hudson.model.DirectoryBrowserSupport.CSP: "sandbox allow-same-origin allow-scripts; default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src blob: 'self';" I'd really love if we got around to this issue 😆 |
I'd really like to see that feature implemented too. To clarify, there is an official list of Jenkins features controlled by system properties here. Some values like
Another striking example is the server timezone, which requires something like
It would be very nice to have these values handled by CasC, this would help getting rid of the |
The problem with #1204 is you would have another chicken and egg problem (at least with the current implementation) 😭 |
as mentioned in #1204 system properties need to be set much earlier than configuration as Jenkins and/or plugins can change behaviour based on them and they are not expected to change post initialisation. |
I assume you would run it as the very first configurator, possibly even in an earlier initialiser? |
We could add support for it directly in the Jenkins core 🤷♂ . Even with YAML input, why not |
are there any updates? |
Jenkins core has an engine for defining system properties on the flight (SystemProperties in the code or just non-final static fields). It would be great to support such engine in the Condifugation-as-Code plugin
The implementation is TBD
The text was updated successfully, but these errors were encountered: