Issue Details (XML | Word | Printable)

Key: BAM-505
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Steve Smith [Atlassian]
Votes: 0
Watchers: 0
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Bamboo

Bamboo may pickup wrong java installation in sub-processes

Created: 28/Nov/06 06:15 PM   Updated: 17/May/07 02:15 AM
Component/s: Build Process
Affects Version/s: None
Fix Version/s: 1.1.1

Time Tracking:
Not Specified

Environment: Bamboo/Tomcat started from daemontools
Issue Links:
Reference
 

Participants: Mark Chaimungkalanont [Atlassian] and Steve Smith [Atlassian]
Since last comment: 1 year, 34 weeks, 2 days ago
Number of comments: 1
Internal Priority: 2. High
Internal Work Bucket: Confirmed
Labels:


 Description  « Hide
You may remember that opensource.bamboo.atlassian.com would fail to build struts2, failing because java couldn't be found by sub-processes. This was fixed by explicitly setting the path to include the default java.

However this raises the question of whether the build/tests are being run with the correct java SDK. For example, if I have JDK1.5 installed system-wide but nominate to build with JDK1.4 it is likely that JDK1.5 will run unit-tests (and possibly build the project?) rather than the nominated build environment, as maven2 doesn't explicitly specify the java executable path, and the default javac/java will be picked-up.

A possible solution is to add the $JAVA__HOME/bin to the start of the path.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mark Chaimungkalanont [Atlassian] added a comment - 14/May/07 02:33 AM
Probably related to Sam's BAM-1226 bug