-
Task
-
Resolution: Fixed
-
Minor
-
None
-
-
Jenkins 2.273 29 Dec 2020
Proposed enhancement to answer the need for the Jenkinsfile runner (see here).
The $JENKINS_HOME/init.groovy.d directory should be customizable via a system property.
Open question: should this be more global and treat the other (known) types of hook scripts, or targeting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global.
[JENKINS-63833] Make the init groovy script directory configurable
Description |
Original:
Proposed enhancement to answer the need for the Jenkinsfile runner (see [here|[https://github.com/jenkinsci/jenkinsfile-runner/pull/370]).] The $JENKINS_HOME/init.groovy.d directory should be customizable via a system property. Open question: should this be more global and treat the other (known) types of hook scripts, or targetting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global. |
New:
Proposed enhancement to answer the need for the Jenkinsfile runner (see [here|[https://github.com/jenkinsci/jenkinsfile-runner/pull/370]]). The $JENKINS_HOME/init.groovy.d directory should be customizable via a system property. Open question: should this be more global and treat the other (known) types of hook scripts, or targetting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global. |
Assignee | New: Pierre Beitz [ pierrebtz ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Released As | New: Jenkins 2.273 29 Dec 2020 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
Description |
Original:
Proposed enhancement to answer the need for the Jenkinsfile runner (see [here|[https://github.com/jenkinsci/jenkinsfile-runner/pull/370]]). The $JENKINS_HOME/init.groovy.d directory should be customizable via a system property. Open question: should this be more global and treat the other (known) types of hook scripts, or targetting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global. |
New:
Proposed enhancement to answer the need for the Jenkinsfile runner (see [here|https://github.com/jenkinsci/jenkinsfile-runner/pull/370]).
The $JENKINS_HOME/init.groovy.d directory should be customizable via a system property. Open question: should this be more global and treat the other (known) types of hook scripts, or targetting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global. |
Description |
Original:
Proposed enhancement to answer the need for the Jenkinsfile runner (see [here|https://github.com/jenkinsci/jenkinsfile-runner/pull/370]).
The $JENKINS_HOME/init.groovy.d directory should be customizable via a system property. Open question: should this be more global and treat the other (known) types of hook scripts, or targetting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global. |
New:
Proposed enhancement to answer the need for the Jenkinsfile runner (see [here|https://github.com/jenkinsci/jenkinsfile-runner/pull/370]).
The {{$JENKINS_HOME/init.groovy.d}} directory should be customizable via a system property. Open question: should this be more global and treat the other (known) types of hook scripts, or targeting only init scripts? If I believe the comments in the linked PR, other types of scripts might be needed by the JFR so it might be worth to go global. |