[
https://issues.jenkins-ci.org/browse/JENKINS-12456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Lavoie updated JENKINS-12456:
-------------------------------------
Description:
Plugin that deploys itself automatically on slaves should only deploy if the
slave has some specific labels.
The use case here is that not all our slaves might be related to the plugin it
wants to be installed on.
The labels could start with "jenkins-plugin-" so we know it's for a jenkins
plugin and it could add the plugin name after that prefix so we know which
plugin it is.
This can be applied to hadoop as well as ChromeDriver unless it uses the
configuration of selenium grid v2 "exclude pattern" configuration which is not
the case in the trunk.
Unless this feature can be controlled somewhere that I've not seen, this is
pretty bad to install some stuff on machines that don't need it or will fail to
work because the distant machine is not compatible with the plugin
was:
Plugin that deploys itself automatically on slaves should only deploy if the
slave has some specific labels.
The use case here is that not all our slaves might be related to the plugin it
wants to be installed on.
The labels could start with "jenkins-plugin-" so we know it's for a jenkins
plugin and it could add the plugin name after that prefix so we know which
plugin it is.
This can be applied to hadoop as well as ChromeDriver unless it uses the
configuration of selenium grid v2 "exclude pattern" configuration which is not
the case in the trunk.
Unless this feature can be controlled somewhere that I've not seen, this is
pretty bad to install some stuff on machines that don't need it or will fail to
work because the distant machine is not compatible with the plugin
(ChromeDriver is useless on a unix non-gui slave)
> Automatic deploy script should be deployed only on machines with specific
> labels
> --------------------------------------------------------------------------------
>
> Key: JENKINS-12456
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12456
> Project: Jenkins
> Issue Type: Improvement
> Components: plugin
> Environment: linux ubuntu, Jenkins 1.448
> Reporter: Richard Lavoie
> Labels: ChromeDriver, Selenium, hadoop
>
> Plugin that deploys itself automatically on slaves should only deploy if the
> slave has some specific labels.
> The use case here is that not all our slaves might be related to the plugin
> it wants to be installed on.
> The labels could start with "jenkins-plugin-" so we know it's for a jenkins
> plugin and it could add the plugin name after that prefix so we know which
> plugin it is.
> This can be applied to hadoop as well as ChromeDriver unless it uses the
> configuration of selenium grid v2 "exclude pattern" configuration which is
> not the case in the trunk.
> Unless this feature can be controlled somewhere that I've not seen, this is
> pretty bad to install some stuff on machines that don't need it or will fail
> to work because the distant machine is not compatible with the plugin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
