Documentation for Bamboo 4.0.x. Documentation for earlier versions of Bamboo is available too.

This page describes how to configure a JUnit Parser executable for a Bamboo task.

When creating a new job or configuring an existing one, you need to specify the tasks that will execute the job's builds. You must specify an executable for each task. If you specify an Ant, Grails or Maven executable, you will also need to choose a JDK.

When creating a new plan, you can configure the tasks for the plan's default job.

 An executable is a program external to Bamboo used to automate processes. Generally, executables compile source code to generate compiled executable files (referred to as artifacts in Bamboo). Ant, Maven, MSBuild or PHPUnit are just some examples of executables that can be used as part of your build process.

New executables can be defined as capabilities in Bamboo. Once an executable has been defined in Bamboo, it can be configured as part of a task.

関連ページ

Configuring a JUnit Parser executable for a task

始める前に

  • Bamboo の java ビルダー タスク（Maven など）は、タスクの一部としてテスト情報を解析します。テスト結果がビルダー タスクの一部として生成される場合、テスト タスクを設定する必要はありません。

To configure a JUnit executable for a task:

  1. Navigate to the task configuration for the job (this will be the default job if creating a new plan).
  2. Click the name of the desired JUnit Parser task, or click Add Task and then JUnit Parser if creating a new task.
  3. タスク設定の更新
    • Task Description — Enter a description of the task, for display in Bamboo.
    • Specify custom results directories — Enter the name of the test results directory (or multiple directories, separated by commas). You can also use Ant-style patterns such as */test-reports/.xml. Please specify file path relative to your job build's root directory. Do not specify an absolute path.
      For jobs that use CVS, the job build's root directory is <bamboo-home>/xml-data/build-dir/JOB_KEY/<cvs-module>.
  4. 保存をクリックします。
  • ラベルなし



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.