This page describes how to configure a Bamboo task to use a Maven executable. Apache Maven is a tool used for building and managing Java-based projects.
To configure a Maven task:
- Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
- Click the name of an existing Maven task, or click Add Task and then a Maven option (e.g. Maven 2.x) to create a new task.
Complete the following settings:
A description of the task, which is displayed in Bamboo.
Disable this task
Check, or clear, to selectively run this task.
The Maven executable that is available to perform the task. The executable that you select will become one of the task's (and so, the job's) requirements.
You can add other executables, if required.
The Maven goal that Bamboo will execute.
- You can use '
-D' to define one or more JVM parameters. For example,
-Djava.awt.headless=truewill pass the parameter 'java.awt.headless' with a value of 'true'.
- Multiple maven goals can be specified, separated spaces.
- You can include variables (see Using Global or Build-specific Variables).
Use Maven Return Code
Select to have Bamboo skip log parsing.
The JDKs that are available to perform the task. The JDK that you select will become one of the task's (and so, the job's) requirements.
You can add other JDKs, if required.
Override Project File (Optional: Maven 2.x and later only)
The path to your Maven project file, relative to the working sub directory specified. If this is not specified, Maven will use the
pom.xmlin the root of the working sub directory.
Environment Variables (Optional)
Additional system environment variables that you want to pass to your build. Note that existing environment variables are automatically available to the executable. You can also include Bamboo global or build-specific variables (see Using Global or Build-specific Variables).
Multiple variables should be separated with spaces. Parameters with spaces must be quoted (e.g MAVEN_OPTS="-Xms200m -Xmx700m").
Working Sub Directory
(Optional) An alternative subdirectory, relative to the job's root directory, where Bamboo will run the executable. The root directory contains everything checked out from the job's configured source repository. If you leave this field blank, Bamboo will look for build files in the root directory. This option is useful if your task has a build script in a subdirectory and the executable needs to be run from within that subdirectory.
The build will produce test results
Choose one of the following: Look in the standard test results directory or Specify custom results directories – Specify the alternative directory, relative to the root directory, where test results will be created. You can use Ant-style patterns such as
**/test-reports/*.xml. Bamboo requires test results to be in JUnit XML format. For jobs that use CVS, the root directory is
- You can use '
- Click Save.