[QPID-3402] various issues prevent running the Java test profiles in a Jenkins matrix project

• Type: Test
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.13
• Component/s: Java Tests
• Labels: ant_build_system
• Assignee: Keith Wall
• Reporter: Robbie Gemmell
• Created: 09/Aug/11 19:37
• Updated: 17/Sep/12 14:11
• Resolved: 03/Oct/11 08:49

Description

Various issues prevent running the Java test profiles in a Jenkins matrix project, because use of the matrix results in a workspace path structure containing spaces and parentheses.

• The test exclusion system doesnt work when running the tests in a directory structure including spaces, making all tests execute.
• Some of the tests place paths to files into Connection URL, which cant be parsed due to the parentheses.
• The Java tests try to start an external broker (even the same-vm profiles which use a spawned broker for failover tests) which fails due to the directory structure making the absolute path for the command illegal, but working around this then results in failure to start up due to ClassNotFound exceptions.
• The cleanup commands use absolute paths to the commands, which also fails due to the directory structure.

Issue Links

• relates to: QPID-3515 the qpid-server script does not work correctly if the QPID_HOME or QPID_WORK environment variables contain spaces/parentheses
• relates to: QPID-3513 Avoid use of shell script clean-dir during test cycle