Name

Pre/Post Build Command Plugin

Version

1.1.1

Product Versions

1.2.4

Author(s)

Jonathan Doklovic [developer(at)sysbliss(dot)com]

Homepage

http://blog.sysbliss.com

Price

Free

License

BSD

JavaDocs

 

IssueTracking

http://developer.atlassian.com/jira/browse/BPBC

Subversion URL

https://svn.atlassian.com/svn/public/contrib/bamboo/bamboo-prepostcommand-plugin/tags/1.1.1/ or browse via fisheye

Download JAR

prepost-build-command-1.1.1.jar

Download Source

prepost-build-command-1.1.1-sources.jar

Description/Features

This plugin can run an arbitrary command before a build runs or when a build passes or fails.
The pre command is specified on the Builder Configuration page.
The pass and fail commands are specified on the Post Actions configuration page.
Sysout and Syserr from the command are logged to the bamboo.log file.

Usage

  1. Download and install the plugin into your Bamboo WEB-INF/lib folder
  2. Select your build and edit the Builder Configuration under the Configuration tab.
  3. Enter the complete command line to run before the build in the Command field.
  4. Select your build and edit the Post Actions under the Configuration tab.
  5. Enter the complete command line(s) to run in the Success and Failed Command fields
  6. After each build, the system will run either the Success or Failed command as appropriate if it's filled in

Configuration Details

Each command field will expand the following properties if they are entered:

property

description

${bamboo.buildKey}

the build key. (i.e. PRJ-PLAN)

${bamboo.buildNumber}

the build number. (i.e. 14)

${bamboo.fullBuildKey}

the full build key. (i.e. PRJ-PLAN-14)

${bamboo.buildResultsUrl}

the build results url

Version History

1.1.1

type key summary priority status

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

1.1.0

type key summary priority status

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

1.0.0

type key summary priority status

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Screenshots

Screenshots
  • No labels