This documentation relates to an earlier version of Bamboo.
View

Unknown macro: {spacejump}

or visit the current documentation home.

Bamboo allows you to isolate Maven (2.x or later only) executables on an agent-specific basis. If you configure repository isolation for a particular Maven executable capability, each agent that uses this executable will have its own private Maven 2.x artifacts directory, thereby allowing you to avoid these jar and dependency file corruptions. Each isolated repository directory has the path:

$BAMBOO_HOME/.m2/AGENT-${agendid}/repository

You may want to configure repository isolation for Maven executables, if you run multiple Maven executables on one server machine which run under the same user account on that server, but belong to different Bamboo agents. In this case, the agents will use the same default Maven artifacts directory: $HOME/.m2/repository (or %USERPROFILE%\.m2\repository for Windows-based servers). This is the directory to which Maven dependency jars are downloaded and where project artifacts are installed during the "install" phase of a Maven build.

Hence, problems can arise if Bamboo uses these multiple Maven executables simultaneously. For example, if multiple agents on a single computer, each with a different Maven executable capability, start to run Maven builds simultaneously from the queue, the different Maven executables may attempt to download the same dependency to the same artifacts directory location, resulting in corruption of the downloaded jar and dependency files.

On this page:

Configuring Repository Isolation for Maven Executables

Before you begin:

  • This feature is not available for Maven 1.x executables.
  • When configuring any Maven executables in Bamboo in which you want to force local repository isolation, ensure that the executable label you use is one that identifies it as such — for example, 'Maven 2.x with local repository isolation'.

To configure a new local server Maven capability with repository isolation:

  1. Click the 'Administration' link in the top navigation bar.
  2. Click the 'Server Capabilities' link in the left navigation column to display the 'Server Capabilities' page, which lists all local server capabilities currently defined in your Bamboo system.
  3. In the Add Capability section at the end of this page, choose your executable and enter its details as described:
    • 'Capability Type' — Select 'Executable'
    • 'Type' — Select one of the Maven options (2.x or later)
    • 'Executable Label' — Enter 'Maven with local repository isolation'
      (info) You can use any label you wish. However, it will help you and your Bamboo users if you enter an appropriate executable label that identifies this Maven 2.x executable as one that uses local repository isolation.
    • 'Path' — Enter the path for your Maven executable
  4. Click the 'Add' button.
  5. Click the label for the executable you have just added. The executable capability summary screen will be displayed (see 'Maven 2.x Executable' screenshot below).
  6. Click the 'Edit Capability Configuration' link. The 'Configure Capability' screen will be displayed (see 'Maven 2.x Repository Isolation' screenshot below).
  7. Select the 'Local repository isolation' check box.
  8. Click the 'Save' button.


Screenshot above: Maven Executable


Screenshot above: Maven Repository Isolation

Notes

Related Topics

Configuring a Shared Executable Capability

  • No labels

2 Comments

  1. Barry Nijkamp

    Nov 14, 2011

    This option disappeared in 3.3?

    1. PiotrA

      Dec 01, 2011

      Unfortunately yes, due to regression it had disappeared. But it should be back in 3.4 - BAM-10104



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.