Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12456

Automatic deploy script should be deployed only on machines with specific labels

    XMLWordPrintable

    Details

    • Similar Issues:

      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

        Attachments

          Activity

          darkrift Richard Lavoie created issue -
          darkrift Richard Lavoie made changes -
          Field Original Value New Value
          Description Plugin that deploys plugins automatically on slaves should only deploy if the slave has some specific labels.

          The use case here is that now 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 comes from a jenkins plugin the it could add the plugin name after that prefix so we know which plugin it is.

          This can be applied to selenium grid v2, hadoop as well as ChromeDriver.

          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)
          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 comes from a jenkins plugin the it could add the plugin name after that prefix so we know which plugin it is.

          This can be applied to selenium grid v2, hadoop as well as ChromeDriver.

          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)
          darkrift Richard Lavoie made changes -
          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 comes from a jenkins plugin the it could add the plugin name after that prefix so we know which plugin it is.

          This can be applied to selenium grid v2, hadoop as well as ChromeDriver.

          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)
          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 selenium grid v2, hadoop as well as ChromeDriver.

          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)
          darkrift Richard Lavoie made changes -
          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 selenium grid v2, hadoop as well as ChromeDriver.

          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)
          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)
          darkrift Richard Lavoie made changes -
          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 (ChromeDriver is useless on a unix non-gui slave)
          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
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 142822 ] JNJira + In-Review [ 175761 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            darkrift Richard Lavoie
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: