[
https://issues.jenkins-ci.org/browse/JENKINS-13110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Reilly updated JENKINS-13110:
----------------------------------
Component/s: mongodb
> Automatic tool installer: Install from mongodb.org option doesn't include a
> label field
> ---------------------------------------------------------------------------------------
>
> Key: JENKINS-13110
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13110
> Project: Jenkins
> Issue Type: Bug
> Components: mongodb, plugin
> Environment: Jenkins version 1.455
> Reporter: Sean Reilly
> Priority: Minor
>
> 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.
--
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
