-
Bug
-
Resolution: Fixed
-
Low
-
5.0 M5
-
None
-
None
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.
- is related to
-
CLOV-1290 Clover history report generation may not work with multimodule maven project and relative historyDir path
-
- Closed
-
[BAM-13222] Use an absolute path for Clover history dir for automatic Clover integration
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1433505 ] | New: JAC Bug Workflow v3 [ 3384304 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1406972 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1433505 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 607315 ] | New: Bamboo Workflow 2016 v1 [ 1406972 ] |
Workflow | Original: Bamboo Workflow 2014 [ 595226 ] | New: Bamboo Workflow 2014 v2 [ 607315 ] |
Workflow | Original: Bamboo Workflow 2010 [ 531031 ] | New: Bamboo Workflow 2014 [ 595226 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: To be reviewed [ 10026 ] | New: Resolved [ 5 ] |
Fix Version/s | New: 5.0 [ 29794 ] |
Assignee | New: Marek Parfianowicz [ mparfianowicz ] |
Status | Original: In Progress [ 3 ] | New: To be reviewed [ 10026 ] |