Details
-
Type:
Improvement
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: slave-setup-plugin
-
Labels:None
-
Similar Issues:
Description
It would be very beneficial for each Jenkins node to be self-identifiable, during the setup init() step. The reason is because we also want to run some maintenance/init task before the node can be considered to be added onto Jenkins. So as part of the "connecting/reconnecting" step, it is important for the node to be self-identify and know who is who without running any job to obtain the $NODE_NAME.
Code changed in jenkins
User: Stefan Wolf
Path:
src/main/java/org/jenkinsci/plugins/slave_setup/SetupDeployer.java
http://jenkins-ci.org/commit/slave-setup-plugin/8a70760bd883212cee798047dd7d49ba4ebd7a08
Log:
[FIXED JENKINS-24107] Expose NODE_TO_SETUP_NAME and NODE_TO_SETUP_LABELS for prepare and setup scripts