Uploaded image for project: 'Bamboo'
  1. Bamboo
  2. BAM-13222

Use an absolute path for Clover history dir for automatic Clover integration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Low
    • Resolution: Fixed
    • Affects Version/s: 5.0 M5
    • Fix Version/s: 5.0
    • Component/s: None
    • Labels:
      None

      Description

      See problem described here:
      https://confluence.atlassian.com/display/CLOVERKB/Multi-module+Maven+build+on+Bamboo+with+Clover+history+reports

      Bamboo uses default '-Dmaven.clover.historyDir=.cloverhistory' location, which is relative and build fails for sub-modules. Users are not able to override this setting (if they define the property in 'Goals' field in 'Maven Task' configuration, the mvn command is executed with two options - one from user and one from Bamboo).

      Instead of this Bamboo shall explicitly use the absolute path pointing to a workspace root, e.g.:

      -Dmaven.clover.historyDir=${bamboo.build.working.directory}/.cloverhistory
      

      Affects all Bamboo versions.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              mparfianowicz Marek Parfianowicz
              Reporter:
              mparfianowicz Marek Parfianowicz
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: