Issue Details (XML | Word | Printable)

Key: BAM-1011
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Mark Chaimungkalanont [Atlassian]
Reporter: Sam Berlin
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Bamboo

bamboo.home is not a valid environment variable

Created: 12/Mar/07 03:41 PM   Updated: 03/May/07 06:33 AM
Component/s: Infrastructure, Installation
Affects Version/s: 1.0.1
Fix Version/s: 1.1

Time Tracking:
Not Specified

Environment: Linux, bash

Internal Priority: 3. Medium
Participants: Jari Saukkonen, Mark Chaimungkalanont [Atlassian] and Sam Berlin
Since last comment: 1 year, 18 weeks, 1 day ago
Number of comments: 4
Labels:


 Description  « Hide
I am attempting to setup a wrapper start script that sets all necessary environment variables and then starts bamboo, so that we don't have to redo scripts every time we update bamboo. This includes attempting to set the 'bamboo.home' variable, which should work according to the bamboo-init.properties file (I do not want to have to re-edit that file after every upgrade). However, "bamboo.home" is not a valid environment variable name because it contains a period in it. Please consider replacing this variable with something that does not include a period, or allowing an additional parameter so Linux run scripts can set it.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Mark Chaimungkalanont [Atlassian] added a comment - 13/Mar/07 02:15 PM
Perhaps if it can't find anything, it can default to BAMBOO_HOME instead

Jari Saukkonen added a comment - 20/Mar/07 06:10 AM
As of 1.0.2 this can be achieved by setting -Dbamboo.home=<dir> as a JVM parameter.

Sam Berlin added a comment - 20/Mar/07 09:37 AM
AFAIK, there is no way for a wrapper start script to inject parameters into bamboo's start script, which makes upgrading Bamboo using the standalone installation a tedious task. If the start script used some parameters such as JAVA_OPTS and did something like:
java $JAVA_OPTS bamboo.jar $BAMBOO_OPTS
where BAMBOO_OPTS is built it up the parameters required to setup Bamboo correctly & JAVA_OPTS is JVM params, it would make upgrading a lot easier.

(This also applies to allowing the wrapper script to set the web-context-path & port that Bamboo starts up with.)


Mark Chaimungkalanont [Atlassian] added a comment - 03/May/07 06:32 AM
BAMBOO_HOME can now be used as the home variable. Bamboo will still look for bamboo.home first. If it can't find it, then it'll look for BAMBOO_HOME