Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. "Enable Deployable in BuildMaster": selectively enables deployables for a release
    1. In BuildMaster you must ensure that Deployables are disabled by default for a release
    2. The "Select BuildMaster Application" Deployable option must be set to the correct deployable
  2. "Copy Previous Build's Variables": if checked will gather the variables from the previous build and add them to the list of variables being passed in for this build, overriding any that are being set for this build.
    1. This could be useful if you're only passing in pointers to a version, eg you keep your artficats in Artifactory or Nexus
      

Waring: This has not been fully tested, I'm in disucussion with Inedo to resolve the following questions/issues:

...

Warning: If three different jobs request a new build at the same time the first to get in will be fine, the remaining two may encounter a race condition, especially if "Copy Previous Build Variables" is selected. It is unlikely to happen but I am investigating the possibility of queuing this step across all Jenkins builds.

History

Version 1.

...

2 (May

...

14, 2015)
  • Ensure build plugin for Java 1.7
  • Create Build waits for previous execution on BuildMaster to finish before new one is requested
  • Improved wait for build to complete handling
  • Create Build request triggers build regardless of whether BuildMaster application has build step or not
Version 1.0 (May 1, 2015)

...