[#BAM-2358] Can't Find JUnit Results

Bamboo

Can't Find JUnit Results

Created: 11/Mar/08 11:15 AM Updated: 01/Apr/08 07:17 PM

Component/s:

Tests

Affects Version/s:

2.0 beta 4

Fix Version/s:

2.0 beta 8, 2.0

Time Tracking:

Original Estimate:

2 hours

Remaining Estimate:

0 minutes

Time Spent:

2 hours

Issue Links:

Duplicate

This issue is duplicated by:

~~BAM-2403~~ The The Test Results Directory value is not used by the builder

Internal Priority:	2. High
Participants:	Benjamin Damm, Brydie McCoy [Atlassian], Mark Chaimungkalanont [Atlassian] and Sam Berlin
Since last comment:	23 weeks, 3 days ago
Number of comments:	4
Labels:

Description

« Hide

The plan is setup to retrieve the module 'comp-test' from CVS. 'comp-test' is setup as an alias module, retrieving 'components' and 'lib'. This results in the following directory structure:

$BAMBOO_HOME/data_20/xml-data/build-dir/LW-C2T/comp-test
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-C2T/comp-test/components
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-C2T/comp-test/lib

The builder has the 'Working Sub Directory' set to 'components', and runs an ant task.

The 'Specify Custom Results directories' is set to: 'components/all/testData/xml/*.xml' . In Bamboo 1.2.4 this worked. In Bamboo 2.0, I need to prepend that by 'comp-test/' in order for it to find the tests. Not sure which way is right (ie, if it worked because of a bug in Bamboo 1.2.4), but it should somehow be compatible with the Bamboo 1.2.4 data (if by upgrading it because of an upgrade task, or otherwise).

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Sam Berlin added a comment - 11/Mar/08 12:07 PM

FYI, the 'Working Sub Directory' doesn't seem to be a part of the issue – just the fact that is was an alias module. Another plan checks out 'limewire', which is an alias for a series of things, but also includes data in 'limewire' itself, resulting in the layout:

$BAMBOO_HOME/data_20/xml-data/build-dir/LW-INDTESTS/limewire
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-INDTESTS/limewire/core
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-INDTESTS/limewire/gui
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-INDTESTS/limewire/tests
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-INDTESTS/limewire/components
$BAMBOO_HOME/data_20/xml-data/build-dir/LW-INDTESTS/limewire/lib

No 'Working Sub Directory' is set, but the 'Specify Custom results directory' used to be:
tests/testData/xml/*/.xml, components/all/testData/xml/*/.xml
and it can't find the results.

After changing it to:
limewire/tests/testData/xml/*/.xml, components/all/testData/xml/*/.xml

things starting working.

[ Permlink | « Hide ]

Benjamin Damm added a comment - 13/Mar/08 03:21 PM

Thanks for your bug filing! We were having the same trouble, and after seeing this issue, I tried prefixing the path to the test results with our top-level directory name. After prefixing, Bamboo 2.0 beta 5 was able to find the test results.

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 13/Mar/08 06:33 PM

Guys,

Sorry about this. We'll get this fixed up...

Although fixing it up will actually mean that the old behaviour (1.2.4) is kept so your changes will break again. (ie you'll have to remove the module definitions). I'd probably recommend a clean import from 1.2.4 in any case.

Cheers,

Mark C

[ Permlink | « Hide ]

Benjamin Damm added a comment - 18/Mar/08 07:23 PM

Thanks for the fix and the heads up!