Configuring Bamboo Server on start-up

Configuring Bamboo's start-up parameters under Linux

Bamboo on Linux/Unix can be started by either executing the bamboo.sh script or using the wrapper. Either way, the Bamboo server can be customised at start-up.

Bamboo 3.1 and above: Modifying the wrapper.

The wrapper reads the configuration from wrapper.conf found in ../<BAMBOO_INSTALL>/conf. (The properties are documented inside the file.)

Bamboo 3.0 and below: Modifying the bamboo.sh script.

The bamboo.sh script takes four parameters: start|stop|restart|status.

To customise these parameters at startup , edit the $RUN_CMD variable:

#
#This is how the Bamboo server will be started
#
RUN_CMD="java -Xms256m -Xmx512m -Djava.awt.headless=true -classpath $CLASSPATH -Dorg.mortbay.xml.XmlParser.NotValidating=true -Djetty.port=8085 com.atlassian.bamboo.server.Server 8085 ./webapp /"

• java -Xms256m -Xmx512m specifies the minimum and maximum Java Heap size.
• -classpath $CLASSPATH sets the class path at startup.
• -Djetty.port=8085 specifies the port number for the Jetty server.
• com.atlassian.bamboo.server.Server 8085 ./webapp / is the main class that will be executed followed by the context path.

In some cases it might be useful to increase the PermGen space. To do this, add the following parameter to the RUN_CMD variable: "XX:MaxPermSize=512m". This will set the PermGen space to 512mb next time Bamboo is run.

Configuring Bamboo's start-up parameters under Windows

Bamboo can be started in Windows with the startup.bat file (from the command line) or  as a Windows Service. Both use the wrapper to start Bamboo. As in Linux (see above), the wrapper reads the configuration from wrapper.conf. Please edit the .../conf/wrapper.conf file (situated in the root of your Bamboo_Installation directory) as required.
For example to to add more java parameters to the bamboo process extend the parameter list

wrapper.java.additional.1=-Dorg.mortbay.xml.XmlParser.NotValidating=true
wrapper.java.additional.2=-XX:MaxPermSize=256m
wrapper.java.additional.3=-Djava.awt.headless=true
wrapper.java.additional.4=-D<your-parameter>

Configuring Bamboo runtime parameters for bamboo.war

The application container that deploys bamboo has to be configured with the additional java parameter.

Example Tomcat:

...
JAVA_OPTS="-server -XX:MaxPermSize=256m -Dbamboo.home=/path/to/bamboo-tomcat-home -Xmx512m -Djava.awt.headless=true -D<your-parameter>=<value> $JAVA_OPTS"
export JAVA_OPTS
...

Configuring Bamboo agent on start-up

Configuring Bamboo agent service

Bamboo agent uses the same wrapper as the server. If you are running Bamboo as a service, then edit the conf/wrapper.conf file in <Bamboo-Agent-Home>

For example to to add more java parameters to the bamboo process extend the parameter list

wrapper.java.additional.1=-Dorg.mortbay.xml.XmlParser.NotValidating=true
wrapper.java.additional.2=-XX:MaxPermSize=256m
wrapper.java.additional.3=-Djava.awt.headless=true
wrapper.java.additional.4=-D<your-parameter>

Configuring classic Bamboo agent

To apply additional properties to the classic Bamboo agent append the system to the start-up command.

In the example below, we are specifying a Bamboo Home for the agent by adding -Dbamboo.home system property during startup:

// Without a Bamboo Home specified
java -jar  bamboo-agent-2.6.2.jar http://192.168.35.128:8085/bamboo/agentServer/
// With a Bamboo Home specified
java -jar -Dbamboo.home=/bamboo/home bamboo-agent-2.6.2.jar http://192.168.35.128:8085/bamboo/agentServer/