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

improve app detection process

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Minor Minor
    • app-detector-plugin
    • None

      Currently I wonder whether my usage of this plugin is wrong. For a new app (or a new version of an app) I typically do the following:

      1. I install the app (or new version) on the slaves.
      2. I change the inline Groovy code (at "Configure system") to support app/new version.
      3. I test it there.
      4. For all my slaves I then do
        1. disconnecting the slave
        2. reconnecting the slave
        3. wait until detected labels are updated

      Now I wonder whether I can avoid the disconnect-reconnect steps. Can I trigger the app detection for a slave while keeping it connected? Maybe by using some Groovy code from within the "Script Console"?

      Or can I run the app detection automatically on a regular base, e.g. once each hour?

      Or is my depicted procedure completely wrong?

            justice3120 Masayoshi Sakamoto
            heiko_nardmann Heiko Nardmann
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: