Extra Tool Installers1.0Minimum Jenkins requirement: 2.60.3ID: extra-tool-installers

Installs: 397
Last released:
Maintainers
Oleg Nenashev
Peter Darton

Jenkins Plugin Jenkins Plugin Installs Build Status

Features

Plugin provides following installers:

  • Batch command installer for Windows.
    • This is functionally similar to the core code BatchCommandInstaller, but this one performs variable substitution on the batch script before it is executed.
    • Useful when you want your installation script to take node-specific variables into account.
  • Install from a specified folder
    • Setup without any actions. e.g. where the "installation" already exists.
      • Useful when a tool is pre-installed on nodes matching a particular label expression
  • Skip or fail installation
    • Prints warnings during the installation and/or fails the installation
      • Useful when a tool is not available on nodes matching a particular label expression
  • Download (with basic authentication) and extract a zip/tar.gz
    • This is functionally similar to the core code "Extract .zip/.tar.gz" installer, but this supports HTTP Basic Authentication for the download.
      • Useful when you need to download from servers that do not permit anonymous downloads.
  • Try any of ...
    • Used to try (and possibly re-try) one or more nested installers until one succeeds.
    • Useful when using e.g. Extract .zip/tar.gz installers that are downloading from URLs which cannot be relied upon.

Example usage

The following examples use the Custom Tools plugin to illustrate the new installation methods.

Linux-only

This example causes builds to fail if they require the "Very useful Linux tool" but are run on a node tagged with "windows". Nodes tagged with "linux" put ${PATH_TO_THE_TOOL} on the $PATH and $LD_LIBRARY_PATH before they continue on with the build.

Coping with unreliable servers

This example defines a tool with two possible sources from which it can be downloaded.

  1. Jenkins will start by attempting to download the tool from the first server, https://some.unreliable.internal.server.com, done using an HTTP GET with basic authentication using the "myUser" credentials.
  2. If that fails, Jenkins will attempt that URL once more (2 times total, as specified by the last field) before moving on to the next installer, which will also be attempted up to 2 times etc.
  3. The whole set of installers will be looped through a total of 3 times (as specified by the last-but-one field) before giving up.

i.e. up to 12 download attempts in total (aabbaabbaabb)

See also

ArchivesGet past versions
Links
Labels