Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Dynamic Axis on the plugin site for more information.

This plugin allows you to define a matrix build axis that is dynamically populated from an environment variable:


Environment variables can be contributed to a build from a number of places, including:

  • Build parameters
  • Build node configuration
  • Jenkins configuration
  • System environment

When specifying a variable for an axis only the last category of variables can be validated. This is because Jenkins contributes the other types of variables only at actual build time, thus they are not available at configuration time.

Configuring an axis is otherwise the same as for the User-defined axis option: specify an axis name to be used in your build along with the name of the environment variable to dynamically retrieve the axis values from. The rules for the value of this variable are the same: one or more values separated by a space.


Some portable environment variable names include:

  • AXES

The following are all valid values for the contents of the environment variable selected for an axis:

  • dev tst sit
  • jdk6 jdk7
  • deploy_srv1 deploy_srv2 deploy_srv3


Many thanks to Emanuele Zattin for leading the way with the Groovy Axis plugin. And of course to Koshuke, for continuing to expand and improve this excellent platform.

Change Log

Version 1.0.3 (7 December 2014)

  • (error) Properly tokenize axis values when the input variable contains quotes (JENKINS-25660)
  • (error) Prevent ConcurrentModificationException on massive matrix runs (JENKINS-22652)

Version 1.0.2 (29 October 2012)

  • Added fix for synchronization issues, contributed by Nathan Grunzweig

Version 1.0.1 (13 November 2012)

  • Initial release


  1. Unknown User (intel352)

    @kckane, could you explain any impact on a job that uses this extension?  If the axes are generated dynamically, per build, what happens to the overall job statuses that display on the job page itself (not build specific)?

    It seems this could be quite useful, as the number of *possible* axes intersections that I have, are much larger than the actual intersections per build, so it would be nice to reduce the matrix to actual combinations executed...

  2. Unknown User (felarcad)

    What license covers this plugin?

  3. Unknown User (djmille1)

    My company will not permit me to download and use this plugin without our legal department first reviewing the license.  Can you tell me what license applies to this, or include it as a file in this repo?  Thanks!