-
New Feature
-
Resolution: Fixed
-
Major
Issue for https://github.com/jenkinsci/jenkins/pull/1914
Goals:
- Allow the specification of system properties in context.xml in addition to in environment variables
- Avoid having to edit tomcat's systemd.service file to run Jenkins with flags.
- Avoid having to restart app server if flags are changed in context.xml.
- Makes it easier for Jenkins to coexist with other apps on the same app server.
- Centralize parsing of system properties:
- over time, consistent error reporting can be implemented for malformed system properties. Right now, that code is all over the place (e.g. what is and isn't true or false in boolean values is implemented differently)
- access to system properties is now logged, which helps with debugging setups
- is related to
-
JENKINS-34854 Some properties missed in the introduction in SystemProperties
-
- Resolved
-
[JENKINS-34755] Allow setting of system properties from context.xml in addition to setting from command line
Priority | Original: Minor [ 4 ] | New: Major [ 3 ] |
Description |
Original:
Issue for https://github.com/jenkinsci/jenkins/pull/1914 Goals: * Allow the specification of system properties in context.xml in addition to in environment variables * Avoid having to edit tomcat's systemd.service file to run Jenkins with flags. * Avoid having to restart app server if flags are changed in context.xml. * Makes it easier for Jenkins to coexist with other apps on the same app server. * Centralize parsing of system properties: * over time, consistent error reporting can be implemented for malformed system properties. Right now, that code is all over the place (e.g. what is and isn't true or false in boolean values is implemented differently) * access to system properties is now logged, which helps with debugging setups |
New:
Issue for https://github.com/jenkinsci/jenkins/pull/1914 Goals: * Allow the specification of system properties in context.xml in addition to in environment variables * Avoid having to edit tomcat's systemd.service file to run Jenkins with flags. * Avoid having to restart app server if flags are changed in context.xml. * Makes it easier for Jenkins to coexist with other apps on the same app server. * Centralize parsing of system properties: ** over time, consistent error reporting can be implemented for malformed system properties. Right now, that code is all over the place (e.g. what is and isn't true or false in boolean values is implemented differently) ** access to system properties is now logged, which helps with debugging setups |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue is related to |
Workflow | Original: JNJira [ 170937 ] | New: JNJira + In-Review [ 198989 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |