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

Automatic tool installer: Install from mongodb.org option doesn't include a label field

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: mongodb-plugin
    • Labels:
      None
    • Environment:
      Jenkins version 1.455
    • Similar Issues:

      Description

      I first noticed this with the MongoDB plugin (v 1.1), but then realised that this occurs with all automatic tool installers that I can find.

      When choosing an automatic tool installer of type "Extract *.zip/*.tar.gz", or "Run Command", the UI provides a "label" field, which can be used to configure which kinds of nodes use a specific installer. When I have slaves on many platforms, this allows me to install (for example) the mongodb-linux-x86_64 build on a linux slave, and a mongo osx build on an osx slave.

      The "Install from mongodb.org" option doesn't include a label field, even though I can configure multiple installers for different platforms. The first installer is always used no matter what.

      Update: while writing this bug report, I realised that this behaviour seems to be present for all "Install from XXXX" options, across many plugins.

      This behaviour is fine for a platform independent tool like ant, but doesn't work well for native code (such as mongodb).

      Workaround
      Create "Extract *.zip/*.tar.gz" installers with appropriate labels and download locations such as "http://downloads.mongodb.org/linux/mongodb-linux-x86_64-2.0.3.tgz" to accomplish the same thing. Note that this won't work for more complicated automated tool installers like the one that installs java from java.sun.com.

        Attachments

          Activity

          Hide
          bor_georgiev Boris Georgiev added a comment -

          I'm currently experiencing the same problem, but in my case the JDK installer works correclty on both Windows and Linux systems. The problem seems to be present only in installers extending the DownloadFromUrlInstaller.

          Show
          bor_georgiev Boris Georgiev added a comment - I'm currently experiencing the same problem, but in my case the JDK installer works correclty on both Windows and Linux systems. The problem seems to be present only in installers extending the DownloadFromUrlInstaller.
          Hide
          bor_georgiev Boris Georgiev added a comment - - edited

          The json file given as an example on https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer does not seem to contain any information about the OS which the described installer is applicable for, so the hudson.tools.DownloadFromUrlInstaller.Installable does not contain a field with OS information so it is obviously not implemented. I'll try to contribute a patch for this in a few weeks, but it will be good if someone more experienced comments if I'm on the right track .

          Show
          bor_georgiev Boris Georgiev added a comment - - edited The json file given as an example on https://wiki.jenkins-ci.org/display/JENKINS/Adding+tool+auto-installer does not seem to contain any information about the OS which the described installer is applicable for, so the hudson.tools.DownloadFromUrlInstaller.Installable does not contain a field with OS information so it is obviously not implemented. I'll try to contribute a patch for this in a few weeks, but it will be good if someone more experienced comments if I'm on the right track .

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            seanjreilly Sean Reilly
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: