-
New Feature
-
Resolution: Unresolved
-
Major
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid.
That same validation script/command can also be used to auto-detect whether some label is applicable to any slave that comes online and automatically update its labels accordingly.
For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly.
If python 2.6 was replaced by python 3.3 on the system and therefore only python version 3.3 is found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' becomes valid and should be added. The general 'python' label will still be valid and remains unchanged.
In the label configuration page, the user may then choose between the verification and auto-detect option for each individual label.
A logging feature may be desired, so the administrator knows which labels were added or stripped automatically by the plug-in.
[JENKINS-24058] Allow label auto-detection in addition to verifying existing labels using the same validation command.
Description |
Original:
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to auto-detect whether some label is applicable to any slave that comes online. For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 3.3 was found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' is valid and should be added. The general 'python' label will still be valid and remains unchanged. In the label configuration page, the user may then choose between the verification and auto-detect option for each individual label. |
New:
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to auto-detect whether some label is applicable to any slave that comes online. For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 3.3 was found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' is valid and should be added. The general 'python' label will still be valid and remains unchanged. In the label configuration page, the user may then choose between the verification and auto-detect option for each individual label. Edit: A logging feature may be desired, so the administrator knows which labels were added or stripped automatically by the plug-in. |
Description |
Original:
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to auto-detect whether some label is applicable to any slave that comes online. For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 3.3 was found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' is valid and should be added. The general 'python' label will still be valid and remains unchanged. In the label configuration page, the user may then choose between the verification and auto-detect option for each individual label. Edit: A logging feature may be desired, so the administrator knows which labels were added or stripped automatically by the plug-in. |
New:
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to *auto-detect* whether some label is applicable to any slave that comes online and *automatically update* its labels accordingly. {quote} For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 3.3 was found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' is valid and should be added. The general 'python' label will still be valid and remains unchanged. {quote} In the label *configuration page*, the user may then choose between the verification and auto-detect option for each individual label. A *logging* feature may be desired, so the administrator knows which labels were added or stripped automatically by the plug-in. |
Labels | Original: slave slaves | New: label labels slave slaves |
Description |
Original:
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to *auto-detect* whether some label is applicable to any slave that comes online and *automatically update* its labels accordingly. {quote} For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 3.3 was found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' is valid and should be added. The general 'python' label will still be valid and remains unchanged. {quote} In the label *configuration page*, the user may then choose between the verification and auto-detect option for each individual label. A *logging* feature may be desired, so the administrator knows which labels were added or stripped automatically by the plug-in. |
New:
The current plug-in looks at the labels of a slave that comes online and verifies if those labels are still valid. That same validation script/command can also be used to *auto-detect* whether some label is applicable to any slave that comes online and *automatically update* its labels accordingly. {quote} For example, Jenkins could check the installed python version whenever a slave comes online and update (i.e. add, remove or replace) that slave's labels accordingly. If python 2.6 was replaced by python 3.3 on the system and therefore only python version 3.3 is found, label 'python-2.6' is no longer valid and should be removed and label 'python-3.3' becomes valid and should be added. The general 'python' label will still be valid and remains unchanged. {quote} In the label *configuration page*, the user may then choose between the verification and auto-detect option for each individual label. A *logging* feature may be desired, so the administrator knows which labels were added or stripped automatically by the plug-in. |
Workflow | Original: JNJira [ 156930 ] | New: JNJira + In-Review [ 179445 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |