Bamboo Installation Guide

1. Introduction
2. Prerequisites
3. Installation Steps
3.1. Extract Artefacts
3.2. Set Environment Variables
3.3. Create Bamboo Home directory
3.4. Check Folder Permissions
3.5. Install Bamboo as a Windows Service
3.6. Run Bamboo Configuration Wizard
3.6.1. Give License Information
3.6.2. Configure Database
3.6.3. Setup Admin User
3.7. Enable HTTPS
3.7.1. Import Certificates
3.7.2. Update Jetty Configuration
3.7.3. Update Bamboo's Java Service Wrapper Configuration
3.7.4. Restart the Bamboo Service
4. Integration Steps
4.1. Integration Prerequisites
4.2. Import Plans
4.2.1. Export Old Bamboo Plans
4.2.2. Import Bamboo Plans
4.2.3. Reconfigure Bamboo-Crowd Integration
4.3. Add Plugins
4.4. Configure Single-Sign-On
4.4.1. Update Bamboo's Authentication class
4.5. SMTP Configuration
4.6. Update Fortify Configuration
4.7. Import Trusted Certificates
4.8. Add Artifactory and Sonar Plugins
4.9. Add Application Links
4.10. Configure Maven
5. Verification

1. Introduction
This page details how to install and configure Bamboo, and how to integrate it with Crowd, Artifactory, Sonar, JIRA and Confluence.

2. Prerequisites
The following AIS packages must exist on the machine:
atlassian-bamboo-5.0.zip
apache-maven-3.0.5-bin.zip
python_install.zip
HP_Fortify_SCA_and_Apps_3.50_Windows_x64.exe
portecle-1.7.zip
bambooPlugins.zip
The AIS team should have already installed the following products:
HP Fortify, in 'D:\Program Files\Fortify Software\'
Java JDK 1.7.0_25, in 'D:\Program Files\Java\'
The Bamboo Service Account exists
The SSL Certificates have been provided (Bamboo's Key Pair file, and the Root and Intermediate certificates)
Firewall ports have been opened

3. Installation Steps

Extract Artefacts
E

Extract the zip file 'atlassian-bamboo-5.0.zip' into the 'D:\devtools\Bamboo' directory, and rename the resulting 'atlassian-bamboo5.0' folder as 'install', so you end up with the contents of the zip file directly under the D:\devtools\Bamboo\ins folder.

E
E

Extract the other archives to D:\devtools\

Rename the 'apache-maven-3.0.5' folder to 'maven'

Set Environment Variables

E
E

Set the JAVA_HOME system variable, pointing it to the installation of Java in D:\Program Files\Java\jdk1.7.0_25
Add 'D:\Program Files\Java\jdk1.7.0_25\bin;D:\devtools\maven\bin' to the PATH system variable

Create Bamboo Home directory

E

Create the 'D:\devtools\Bamboo\home' directory

E
Update the 'bamboo-init.properties' file located in the 'D:\devtools\Bamboo\install\webapp\WEB-INF\classes' directory, with
the reference to the newly created bamboo-home directory, ensuring you use forward-slashes instead of backslashes:

bamboo.home=D:/devtools/Bamboo/home

3.4. Check Folder Permissions

As the bamboo service will be running under a service account, the service account will need full access to the 'install' and 'home' folders the
properties dialog for each of these folders, check that the bamboo service account has modify access. If it doesn't, follow these instructions:
E
E

Go to the 'Security' tab

Click on the 'Edit' button to change permissions
E
Click on 'Add' and enter the service name into the text field, then click 'Check Names'. Once the name has resolved to it's
full account name, you can then click 'OK'.
Select the Service Account name in the top list, and then select the 'Full control' checkbox to give the service account full access to
the folder, then press 'OK' twice.

Install Bamboo as a Windows Service

E
E
E

In windows explorer, navigate to 'D:\devtools\Bamboo\install', and right-click on the batch file called 'InstallAsService.bat'. Select 'Run
as administrator'. You'll see a cmd prompt screen come up, then disappear straight away.
In the windows 'run' dialog, type 'services.msc' to open up the Windows Services console, and check to see that it has created a
service called 'Bamboo build server'.
Double-click on the 'Bamboo build server' service, and change the 'Startup type' to 'Automatic' and click 'Apply'. Sometimes process
will set to 'Automatic' by default.
E
Go to the 'Log On' tab, and select the 'This account' option, click 'Browse' and enter the service account name:
'GLOBALTEST\AUBamboodsa', then click 'Check Names' to ensure it finds the right service account, then click 'OK'.
Enter the password for the service account, then click 'OK'.
E
Right-click the 'Bamboo build server' service, and select 'Start'. You should now be able to open
the 'D:\devtools\Bamboo\home\logs\atlassian-bamboo.log' file and see that bamboo starts up
successfully.

Run Bamboo Configuration Wizard



Give License Information

In a web browser on the bamboo machine, navigate to 'http://localhost:8085',and run through the setup wizard.
E
When prompted, use the ServerID value from bamboo to retrieve the license key from the my.atlassian.com account.
Paste this license into the relevant field in the bamboo interface.
Configure Database

E
E
E

In the next stage of the configuration wizard, choose 'Custom Installation', as we want to configure bamboo to point to an
external database.
Accept the default values for the General Configuration, select 'Continue'.
Choose 'External Database', and specify the Microsoft SQL Server option from the drop-down list, then click 'Continue'.
Update the database URL to the following value:

jdbc:jtds:sqlserver://SQLAU001MEL0092.global.abc.com:49168/bamboo;useNTLMv2=tr
ue;domain=global

E
E
E


Add the username and password for the bamboo database service account
Click 'Continue'. Bamboo will now load for a while as it updates the database with the necessary data.
Select 'Create a new Bamboo home',then click 'Continue'.
Setup Admin User

Enter the details of the local Administrator user that you will use until the integration with Crowd is complete.

E
User name : bambooadmin
E
password : bambooadmin
E
email : bamboo.admin@gmail.com
Select 'Finish'. The configuration wizard is now complete!

3.7. Enable HTTPS

3.7.1. Import Certificates

Follow the instructions in the SSL Configuration Guide to import bamboo's Key Pair file (bamboo.service.pfx), the ABC Root and Intermediat
certificates, and the Crowd trusted certificate.


Update Jetty Configuration

E
E

Open the Jetty.xml file, which is located in the 'D:\devtools\Bamboo\install\webapp\WEB-INF\classes' directory

Comment out or remove the existing 'addConnector' block, which allows http connections

<!-- <Call name="addConnector">

<Arg>
<New class="org.eclipse.jetty.server.nio.SelectChannelConnector">
<Set name="host"><Property name="jetty.host" /></Set>

<Set name="port"><Property name="jetty.port"

default="8080"/></Set>
<!--<Set name="Host">127.0.0.1</Set>--> <!-<Set name="ConfidentialPort">8443</Set>-->
<!--<Set name="IntegralPort">8443</Set>-->
</New>
</Arg>
</Call>
-->

3. Add the following configuration, which will detail the connector to be used for https connections.

<Call name="addConnector">
<Arg>
<New class="org.eclipse.jetty.server.ssl.SslSelectChannelConnector">
<Arg>

<New class="org.eclipse.jetty.http.ssl.SslContextFactory">
<Set name="keyStore"><SystemProperty name="jetty.home"
default="D:/devtools/Bamboo/install/conf/bambooKeyStore.jks"/></Set>
<Set name="keyStorePassword">changeit</Set>
<Set name="keyManagerPassword">changeit</Set>
<Set name="trustStore"><SystemProperty name="jetty.home"
default="D:/devtools/Bamboo/install/conf/bambooKeyStore.jks"/></Set>
<Set name="trustStorePassword">changeit</Set>
</New>

</Arg>
<Set name="port">443</Set>
<Set name="maxIdleTime">30000</Set>
</New>
</Arg>
</Call>

In the same Jetty.xml file, there is another section under the comment '<!-- Add web applications Context. -->', which is titled '<Ca
name="setHandler">'. Under this tag, update the below values:

...
<SystemProperty name="bamboo.webapp" default="../webapp"/>
...
<Arg name="contextPath">/</Arg>
...

Update Bamboo's Java Service Wrapper Configuration

E
E

Open the file 'wrapper.conf', which exists in the 'D:\devtools\Bamboo\install\conf' directory

Update the 'wrapper.app.parameter.2' property, to change it from a port number to the path to the jetty.xml file

wrapper.app.parameter.2=../webapp/WEB-INF/classes/jetty.xml

Comment out the 3rd and 4th wrapper.app.parameter values, so ensure they won't get used. If they remain uncommented, when
you attempt to start the bamboo service, you'll get NumberFormatExceptions complaining that wrapper.app.parameter.2 cannot be
parsed as a number. If you comment out the 3 and 4 parameters, it will accept parameter 2 as a config file.

#wrapper.app.parameter.3=../webapp
...
#wrapper.app.parameter.4=/

Update the max memory setting to 2GB:

Maximum Java Heap Size (in MB)

wrapper.java.maxmemory=2048

Update java additional properties to point to the custom bambooKeyStore:

#Additional parameters given to enable the use of a custom keystore

wrapper.java.additional.5=-Djavax.net.ssl.keyStore=D:/devtools/Bamboo/install/
conf/bambooKeyStore.jks wrapper.java.additional.6=Djavax.net.ssl.keyStorePassword=changeit wrapper.java.additional.7=Djavax.net.ssl.trustStore=D:/devtools/Bamboo/instal l/conf/bambooKeyStore.jks
wrapper.java.additional.8=-Djavax.net.ssl.trustStorePassword=changeit

Restart the Bamboo Service

E
E
E

Open the services console by typing 'services.msc' in the windows run dialog
Right-click on the 'Bamboo build server' service, and select 'Restart'.
Once bamboo has finished restarting, you should be able to access it from your local machine using https://bamboo.service.abc

4. Integration Steps

Integration Prerequisites
E

All of Crowd's users, groups and applications have been migrated from the old environment into the new enviroment.
E
A new application associated with the new bamboo instance, (eg, 'bambooqa') has been created, along with a new password,
and the relevant groups have been given access (ABC-bamboo-admin, etc).

Import Plans

Importing bamboo plans from one environment to another is not as simple as it should be. Unfortunately there is no way to export just the
plans themselves - when you run an export in bamboo, it will export the user-management data and some other configuration as well,
including the application links, crowd configuration, etc. For this reason, Crowd installation and configuration (including Integration steps)
must be completed prior to executing this step.
Whatever environment you import the plans into must have access to the same admin users as the environment where the export was taken.
As such, here are the steps we followed to get the bamboo plans migrated from the Tactical environment to the QA environment:


Export Old Bamboo Plans

In the tactical environment, login to Bamboo as an admin user, navigate to the 'Administration' tab, and choose the 'Export' link f
underneath the 'System' menu heading.

E
E
E

use the bamboo server by clicking 'Pause Server' at the top of the screen, to ensure there are no jobs running during the
export process. This will prevent the export from becoming corrupted and will prevent any builds from being affected by the
export process.
Take note of the 'Export Directory Path', as you will need to retrieve the export zip file later.
Specify the export file name, and ensure 'Export Results' and 'Export Build Logs' are selected. Ensure 'Export Artifacts' notselecteis
d.
Click the 'Export' button, and wait for the Export to finish.
E
Once the export has finished, retrieve the export file from the bamboo server, and copy it across to the server running
the new bamboo instance.
Import Bamboo Plans

E
E
E

Copy the exported bamboo zip file across to the new bamboo instance
Login to the new bamboo instance
Update the 'User Repositories' page under 'Security' in the Administration page, changing the setting to 'Users and groups from or
Crowd'
E
Update the 'Server URL' value tohttps://crowd'.service.abc/crowd'(assuming crowd has https enabled)
E
Enter in 'bambooqa' as the 'Application name', and the associated password, both of which should match the values giv for
the new application in step 8.1
E
Leave the Cache refresh interval as the default value, and click 'Save'.
E Restart the bamboo service, and ensure you can login with the same administrator account as you can with the old
bamboo instance (this relies upon the crowd instances being synced as per step 8.1
Back in the Administration page, click 'Import' under the 'System' menu, and specify the path to the export zip file

E
E


Leave the other settings as default, with Backup data checked and the other two values unchecked ('Clear artifact directory'
and 'Apply imported data without server shutdown').
Click 'Import', and wait for the import to finish.
Once the import has completed, you will need to restart the bamboo service.
Reconfigure Bamboo-Crowd Integration

Once Bamboo finishes restarting after the import, you will notice that you can no longer login, even if you are using valid admin accounts that
you know exist in both crowd instances. This is because after the import, bamboo is configured to talk to the old crowd instance, which
requires a certificate in order to connect successfully. As this certificate doesn't currently exist, you'll notice a bunch of SSL errors in the log
bamboo started up. This is very simple to fix:
E
E

Login to the bamboo windows server, and navigate to the 'D:\devtools\Bamboo\home\xml-data\configuration' directory, and open th
'crowd.properties' file.
Update the application.name and crowd.base.url values to point to the new crowd instance:

application.name=bambooqa
crowd.base.url=http\://crowd.service.dev\:8080/crowd

Also ensure that the 'application.password' value matches what you specified when creating the application in crowd in step 8.1
E
Restart the bamboo service. Once bamboo has started up again, you should be able to login with the accounts that exist in
crowd, and you should see all of the imported jobs available and editable.

Add Plugins

Retrieve

the

D:\devtools
plugin-1.1.jar

following
a.

plugins

from

bamboo-variable-inject-

E
agent-smith-wallboard-4.4.2.3.jar
Copy the jars across to the Bamboo server to the following location:

D:\devtools\Bamboo\home\plugins

3. Restart the Bamboo service

Configure Single-Sign-On

NOTE:This step requires Crowd to have already been configured with the necessary bamboo Application entry, Directories, users
and groups. You will need to know the application name and password specified in Crowd's bamboo application entry so they can
be entered into Bamboo's configuration.


Update Bamboo's Authentication class

E
E
E

Shut down Bamboo.

Edit the \BAMBOO\webapp\WEB-INF\classes\seraph-config.xml
Comment out the authenticatornode:

<!--<authenticator
class="com.atlassian.bamboo.user.authentication.BambooAuthenticator"/>-->

4. Add a new authenticator, by adding the following tag:

<authenticator
class="com.atlassian.crowd.integration.seraph.v25.BambooAuthenticator"/>

Update the crowd.properties file in 'D:\devtools\Bamboo\home\xml-data\configuration' by changing the session.validationinterval to

non-zero value:

session.validationinterval=30

E
E

In this same crowd.properties file, ensure that the 'application.name' and 'application.password' entries match the values specifie the
Crowd bamboo application configuration.
Start Bamboo. Bamboo's authentication and access request calls will now be performed using Seraph.

SMTP Configuration

Note: You will need to obtain the smtp server details, and some valid credentials to use it.
E
E
E

Login to Bamboo as an Administrator

In the 'Administration' menu, click 'Mail server' under the 'Communication' heading.
Enter the SMTP details and click the 'Save' button:

4.6. Update Fortify Configuration

Since the tactical installation, the location of the Fortify server has been changed.
Server

Hostname

IP Address

Tactical

appau182frm111.oceania.corp.abc.com

10.44.165.11

New

appau001mel0333.global.abc.com

10.44.204.225

Update the file 'server.properties' in the directory 'D:\Program Files\Fortify Software\HP Fortify v3.50\Core\config\' with the new f IP
address in these locations:

rulepackupdate.server=http\://10.44.204.225/ssc/
uploadclient.server=http\://10.44.204.225/ssc/

2. Run the rulepackupdate by opening a cmd prompt and running the rulepackupdate script:

$>fortifyupdate

Bamboo needs to communicate with a number of other applications: sonar, artifactory, jira, etc. This involves installing some Bamboo
plugins, and because each of the applications are SSL enabled, we will need to import some additional Trusted Certificates so that Bamboo
trusts the remote applications it is communicating with.

Import Trusted Certificates

E
E
E
E
E

Follow the instructions in the SSL Configuration Guide under the 'Importing Trusted Certificates' heading, to import the
certificates for the following applications:
sonar.service.dev
artifactory.service.dev
jira.service.dev
confluence.service.dev

Add Artifactory and Sonar Plugins

E
E

Retrieve the bamboo-sonar-tasks-1.8.0.jar from D:\Devtools

Copy the jar to bamboo's plugins directory:

D:\devtools\Bamboo\home\plugins

3. Retrieve the bamboo-artifactory-plugin-1.6.0.jar from D:\devtools

Copy the jar across to the Bamboo server to the following location:

D:\devtools\Bamboo\install\webapp\WEB-INF\lib

E
E
E
E
E
E

Restart the Bamboo service

Login to Bamboo as an administrator, and navigate to the 'Administration' -> 'Plugins' -> 'Artifactory Plugin' screen
Click the 'Edit' link next to the Artifactory Link under the 'Manage Artifactory Servers' section of the page. The existing link is ther
from the import, so will be incorrect for the new servers.
Update the Artifactory URL to point to the new Artifactory instance
The Username and Password fields need to be the credentials used for bamboo to login to Artifactory, so use the 'admin' user
account.
For the password, because we have configured Artifactory to require an encrypted password, we'll need to retrieve the encrypted
password to enter into this bamboo config page.
E
Login to Artifactory as the admin user
E
In the 'Home' tab, select 'Client Settings' -> 'Maven Settings'
E
Select the 'Generate Settings' button
E
Take note of the file name under the 'Target Path' label, and click 'Download Settings'
E
Open the xml file that was just downloaded, and find the '<server>' tag, which will look something like this:

<server>
<username>admin</username>
<password>(removed)</password>
<id>central</id>
</server>

E
E

E Copy the encrypted password from the password field, and enter it in the Password field under the 'Artifactory Server
Details' screen in Bamboo.
Leave the Request timeout as default, and click the 'Test' button to validate the settings.
You should see a green box containing 'Connection Successful!". Click the 'Save' button

Add Application Links

E
E
E
E
E
E

E
E
E

In Bamboo, under the Administration menu, choose 'Application Links'.

Click on the 'Add Application Link' button.
Enter the URL for JIRA - 'https://jira.service.abc'
Make sure the checkbox is checked for the option 'Also create a link from 'TBOS Jira' back to this server'
Enter some administration login details for JIRA
Ensure the 'Reciprocal LInk URL' points back to the correct bamboo URL (ie,https://bamboo.service.abc)
E Note: This step may require you login to the JIRA machine and import bamboo's trusted certificate (following the same
instructions as for step 4.1)
Make sure 'The servers have the same set of users and usernames' is checked, and 'These servers fully trust each other'
Click the 'Create' button.
Follow the same instructions to create another application link to Confluence - 'https://confluence.service.abc'

Configure Maven

Bamboo will execute maven commands during some of the builds. Although we have imported the Artifactory trusted certificate into
Bamboo's keystore, maven does not know about this keystore when connecting to Artifactory to download any necessary dependencies.
Therefore, we need to import the ABC root certificate, intermediate certificate, and the Artifactory certificate into Java's cacerts file so that
maven can connect successfully.
Follow the instructions in section 5 of the SSL Configuration Guide to import the root/intermediate/Artifactory certificates into the following
file: D:\Program Files\Java\jdk1.7.0_25\jre\lib\security\cacerts
Once this has been done, maven will be able to successfully download artifacts through Artifactory.

 Verification
E
E
E
E
E
E

Make sure you can see the login page https://bamboo.service.abc'

Make sure you can login with a crowd user with Bamboo access
Make sure you can't login with a user that doesn't have Bamboo access
Run the 'Security Scan' job, and ensure it executes successfully. This job will verify that the connection to SVN is working properly
and will check that the Fortify Scans can run successfully.
Login to 'https://sonar.service.abc'and check that you can see the results of the fortify scans
Once some bamboo jobs have been run, login to 'https://jira.service.abc'and check the 'Activity Stream' box to ensure you can see
some entries from the Bamboo job executions.

Bamboo Data Migration

Introduction
Bamboo data migration involves exporting all the settings from one instance to another. This is relatively easy, but can only be done in a bigbang approach; there's no way to export a single plan by itself. All build plans and other configuration including user-management data will
be included in the backup.

Backup
In the Source machine, the specific steps to follow to export the bamboo data are detailed in the bamboo install guide, section 4.2.1. This will
generate a zip file containing all the bamboo data, which you can then copy over to the target machine for importing.

Restore
After copying the backup zip file across to the target server, follow the steps in the bamboo install guide, section 4.2.2. This will import the
zip file containing all of the source machine's bamboo configuration.

Post Restore Steps

After Importing the backup zip file, you will no longer be able to login to crowd even with a valid admin user, because bamboo will be
attempting to validate the user against the source machine's crowd instance which requires an SSL certificate to work properly. The steps to
resolve this and get bamboo back up and running successfully are detailed in the bamboo install guide, section 4.2.3.

Bamboo Support Guide

1. Technical Specifications
2. Known Issues
3. Lessons Learnt
4. FAQ
4.1. How can I stop/start/restart the bamboo service?
4.2. What happens if you can not access https://bamboo.service.abc?

5. Certificate Details
6. Housekeeping

1. Technical Specifications
Property

Value (Prod)

Application URL
https://bamboo.service.abc
Machine Name

APPAU001MEL0094.global.abc.com

DNS

bamboo.service.abc

IP address

10.46.167.193

Product Version

5.0

Install Path

D:\devtools\Bamboo\install

Home Path

D:\devtools\Bamboo\home

Log Path

D:\devtools\Bamboo\home\logs

Service Account Name

GLOBAL\AUBamboodsa

Service Name

Bamboo build server

DB

SQLAU001MEL0092.global.abc.com:49168/bamboo

Vendor documentation

https://confluence.atlassian.com/display/BAMBOO/Bamboo+Documentation+Home

2. Known Issues
N/A

3. Lessons Learnt
Maven doesn't know about the bambooKeyStore.jks file, so needs to have the Artifactory and ABC root/intermediate certificates
imported into Java's cacerts file in order to successfully download artifacts.

4. FAQ
4.1. How can I stop/start/restart the bamboo service?
The Bamboo service is managed through the windows service dialog. Open the Run dialog and type 'services.msc'. The service name is
'Bamboo build server'. If you right-click on the service you can start/stop or restart the service from here.

What happens if you can not access https://bamboo.service.abc?

E

RDP into the bamboo.service.dev machine and check that the bamboo service is running.
E This can be done through the Windows Task Manager. Sort the processes by the 'User Name' field, and if Bamboo is
running, there will be java.exe, wrapper.exe and conhost.exe processes running under the 'AUBamboodsa' user.
E
From the services application (services.msc) check the status of the 'Bamboo build server' service; if it is up and running,
the status should be 'started'.
i. If the service is not started, then right-click on the Bamboo service and click 'start'.
E
Check the Logs to see if there are any exceptions. If the log file hasn't been written to, check the security permissions on
the d:\devtools directory. The AUBamboodsa service account must have modify permissions on this directory in order to
write logs.

5. Certificate Details
Property

Value

Keystore (JKS) location

D:/devtools/Bamboo/install/conf/bambooKeyStore.jks

Key Pair alias

bamboo

Truststore location

D:/devtools/Bamboo/install/conf/bambooKeyStore.jks

Trusted Hosts

ABC Root/Intermediate
artifactory
confluence
crowd
JIRA
sonar

6. Housekeeping
Database backup should be taken care of by the DBA team.
Build logs and plan configuration get backed up daily to 'D:\devtools\Bamboo\home\backups'.These backups will gradually get
larger as time goes on and more builds occur. Should disk space be running low, old backups from this directory can be safely
deleted.

Bamboo Known Issues

1. Unable to run plans in bamboo as the remote agent is offline
Symptom:
Initial investigation:
Root Cause:
Resolution steps:
2. Bamboo build fails due to artifactory space issue
Lessons learnt:
3. Build failure issue artifactory proxy issue
Bamboo build tool:
Resolution:
Root Cause:
TeamCity CI tool:
Initial investigation:
Resolution:
Root Cause:
4. Bamboo build fails: working copy of source code is locked
Symptom:
Initial investigation:
Resolution:
Verification:
5. Bamboo-Sonar task failed in bamboo
6. Bamboo crashed due to space issue
Symptom:
Cause
Resolution

1. Unable to run plans in bamboo as the remote agent is offline

Symptom:

User reported the below issue:

Unable to build plan as the system is paused.
Change detection ignored for plan BSTB-FIX, plan cannot be run because the system is PAUSED
Initial investigation:

Checked the Bamboo log in the server and found the below error:

TBOS - fix - dcmw251z-DEV BSTB-FIX-DEVDEPEXT-31 : Agent 'dcmw251z' went offline while building BSTB-FIX-DEVDEPEXT-31. The
build results did not finish.
Root Cause:

Bamboo remote agent was offline in the unix server.

Resolution steps:

Restarted the Bamboo service to resolve the issue.

2. Bamboo build fails due to artifactory space issue

Symptom:
User reported the below issue:
The bamboo build failed due to the below error:
[ERROR] Internal error: java.lang.RuntimeException: Error occurred while publishing artifact to Artifactory: D:\TBOS\DevTOOLS\Bamb
oo\xml-data\build-dir\BSTB-REL-JOB1\tbos-distribution\ibm-was-tbos\tbos-external-config\target\tbos-external-config-1.0.01.19.00.zip. 03Dec-2013 00:03:22 [ERROR] Skipping deployment of remaining artifacts (if any) and build info. Failed to deploy file: HTTP response code:
404. HTTP response message: There is not enough space on the disk
03-Dec-2013 00:03:22 [ERROR] -> [Help 1]
03-Dec-2013 00:03:22 org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Error occurred while
publishing artifact to Artifactory:
D:\TBOS\DevTOOLS\Bamboo\xml-data\build-dir\BSTB-REL-JOB1\tbos-distribution\ibm-was-tbos\tbos-external-config\target\tbos-external-c
onfig-1.0.01.19.00.zip.
03-Dec-2013 00:03:22 Skipping deployment of remaining artifacts (if any) and build info.
03-Dec-2013 00:03:22
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168)
03-Dec-2013 00:03:22
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
03-Dec-2013 00:03:22
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
03-Dec-2013 00:03:22
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
03-Dec-2013 00:03:22
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
03-Dec-2013 00:03:22
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
03-Dec-2013 00:03:22
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
03-Dec-2013 00:03:22
at java.lang.reflect.Method.invoke(Method.java:601)
03-Dec-2013 00:03:22
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
03-Dec-2013 00:03:22
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
03-Dec-2013 00:03:22
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
03-Dec-2013 00:03:22
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
03-Dec-2013 00:03:22 Caused by: java.lang.RuntimeException: Error occurred while publishing artifact to Artifactory:
D:\TBOS\DevTOOLS\Bamboo\xml-data\build-dir\BSTB-REL-JOB1\tbos-distribution\ibm-was-tbos\tbos-external-config\target\tbos-external-c
onfig-1.0.01.19.00.zip.
Initial investigation:
Checked the space in the artifactory server "D:" drive.
Root Cause:
The space in drive was 0 KB
Resolution steps:
Removed the old log files and the back up files to resolve the issue.
Technical verification:
Checked the space in artifactory server.
Business/User communication:
Communicated to the user to run the bamboo plan.
Lessons learnt:

Kept the disk space check in place for the server.

3. Build failure issue artifactory proxy issue

Bamboo build tool:

Symptom:
User reported that the build plan is failing in Bamboo CI tool.

Initial investigation:
Checked the bamboo logs and found the below:
build 30-Oct-2013 18:00:20 [ERROR] Failed to execute goal com.github.mcheely:requirejs-maven-plugin:2.0.0:optimize (optimize) on
project com.abc.web.caas.admin: r.js exited with an error. -> [Help 1]
build 30-Oct-2013 18:00:20 [ERROR]
build 30-Oct-2013 18:00:20 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
build 30-Oct-2013 18:00:20 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
build 30-Oct-2013 18:00:20 [ERROR]
From the artifactory it is found that the proxy in the artifactory is not set to access the github website.
Resolution:

Raise Work Order Request to 'CS messaging' team for adding the URLs referred by the 'Bamboo build plan' to the artifactory server proxw
hite list .
Get the Confirmation from the users about the issue resolution.
Root Cause:

The proxy in the artifactory is not set to access the github website.
TeamCity CI tool:

User reported that the build is failing in TeamCity CI tool.

Initial investigation:

Checked the TeamCity logs and found that the job is failing while trying to execute the artifactory task.
From the artifactory logs it is found that the proxy in the artifactory is not set to access the URLs referred in the TeamCity build plan.
Resolution:

Raise Work Order Request to 'CS messaging' team for adding the URLs referred by the 'TeamCity build plan' to the artifactory server pro
white list .
Get the Confirmation from the users about the issue resolution.
Root Cause:

The proxy in the artifactory is not set to access the github website.

4. Bamboo build fails: working copy of source code is locked

Symptom:

User reported the below issue:

Unable to retrieve source code for revision '1316', plan 'BSTB-FWRK0-JOB1': svn: E155004: Working copy
'D:\TBOS\DevTOOLS\Bamboo\xml-data\build-dir\BSTB-FWRK0-JOB1' locked)
Initial investigation:

Checked the bamboo logs and found the below:

Resolution:

Deleted the data from the below folder:

D:\TBOS\DevTOOLS\Bamboo\xml-data\build-dir\BSTB-FWRK0-JOB1
Verification:

The plan was rerun by the development team and it has completed successfully.
https://confluence.service.abc/display/CONTRN/Bamboo-Sonar+task+failed+in+bamboo

5. Bamboo-Sonar task failed in bamboo

Bamboo-Sonar task failed in bamboo

6. Bamboo crashed due to space issue

Symptom:

Bamboo application is down. Below is the error received from the GUI:

HTTP ERROR: 503

Problem accessing /. Reason:
Service Unavailable
java.io.EOFException: input contained no data.

Cause

Bamboo has been shut down improperly. Possible causes are:

Ran out of disk space on the Bamboo server
Power outage on the Bamboo server

Resolution

Check all files in <BAMBOO_HOME>/xml-data/configuration/*.xml and see if they are ok.

If not please restore these files from a Bamboo backup zip. You can simply unzip the backup and copy the administration.xml file from
the <backup-zip>/configuration directory.
If you don't have a backup you can:
change bamboo.home in <bamboo-install>/WEB-INF/classes/bamboo-init.properties to a temporary location
<temp -bamboo-home>.
if you are using an external database - create a new temporary database for this procedure.
start Bamboo, run through the setup wizard entering the data as if in your production instance (except for db name). File <temp-bam
boo-home>/xml-data/configuration/administration.xml will be created.
copy the above file into <bamboo-home>/xml-data/configuration/.
Double check the copied files for correctness regarding paths and URLs.
This should restore the missing files for your production instance.

Bamboo-Sonar task failed in bamboo

Issue:

The build failed because of the following reason.

13-May-2014 [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project tbos: Can not
21:19:04 execute Sonar: Fail to decorate 'com.abc.services.schedule.IntervalScheduleJob': Unable to persist :
org.sonar.api.database.model.RuleFailureModel@5ba65a63[snapshotId=5045,ruleId=475,priority=MAJOR,message=Variab
'endSecond' must be private and have accessor methods.,line=27,cost=<null>,createdAt=Tue May 13 21:02:45 EST
2014,checksum=63c956ab2caf9d12ec23f56526087bb0,permanentId=<null>,switchedOff=false,personId=<null>,id=<null>]:
org.hibernate.exception.GenericJDBCException: could not insert: [org.sonar.api.database.model.RuleFailureModel]: IO Exception:
"java.io.IOException: There is not enough space on the disk"; "D:/TBOS/DevTOOLS/Sonar/sonar-3.4.1/data/sonar.h2.db"; SQL
statement:

13-May-2014 [ERROR] insert into rule_failures (id, checksum, cost, created_at, line, message, permanent_id, person_id, failure_level,
21:19:04 rule_id, snapshot_id, switched_off) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) [90031-167]
Root Cause:

Incorrect sonar setting were used for the bamboo-sonar plan.Also the driver setting were incorrect for the sonar server configured inside
bamboo.
Resolution:

To update a Sonar Server, simply click on the Edit link next to the server you want to edit on the Sonar Servers list page.
And enter the following parameters:
Name
Description (Optional)

A unique name to identify the server amongst others

Descriptional text of the server

Sonar Host URL

The URL on the Sonar host. The default URL is http://localhost:9000/

If Anonymous Host is unchecked the following are also required:

Username

The Sonar host username, used for authentication, together with the password, on the Sonar host front-end. (Mainly to
display Sonar data on with Bamboo of secured Sonar instances)

Password

The Sonar host password, used for authentication, together with the username, on the Sonar host front-end. (Mainly to
display Sonar data on with Bamboo of secured Sonar instances)

If This server uses the default Datasource is unchecked the following are also required:
URL

The Database JDBC url. You can find this in the sonar.properties file on your Sonar installation. Dont set this if you use the
default embedded database. (example for MySQL: jdbc:mysql://localhost:3306/sonar?useUnicode=true&char
acterEncoding=utf8)

Driver

The Database Driver class name. You can find this in the sonar.properties file on your Sonar installation. Dont set this if you
use the default embedded database. (example for MySQL: com.mysql.jdbc.Driver)

Username

The datasource username used, together with the password, for datasource authentication.

Password

The datasource password used, together with the username, for datasource authentication.

Bamboo DB Usefull Queries

Active Bamboo user list from Crowd tool:

Login to crowd database and run the query

select distinct cu.user_name,cu.first_name,

cu.last_name,cu.email_address,cm.parent_name "Group Name"
from cwd_user cu, cwd_membership cm, cwd_app_dir_group_mapping ca
where cm.child_name=cu.user_name
and ca.group_name=cm.parent_name
and ca.application_id=15892481
--and cu.user_name='dasha1'
and cu.active='T'
and ca.directory_id='32769'
and cu.directory_id=ca.directory_id
order by 1,5

select distinct cu.user_name,cu.first_name, cu.last_name,cu.email_address,cm.parent_name "Group Name"from cwd_user cu,

cwd_membership cm, cwd_app_dir_group_mapping cawhere cm.child_name=cu.user_nameand ca.group_name=cm.parent_nameand
ca.application_id=15892481--and cu.user_name='dasha1'and cu.active='T'and ca.directory_id='32769'and
cu.directory_id=ca.directory_idorder by 1,5

Bamboo FAQ
Bamboo 5.6.1
Bamboo Data Migration Procedure
PrIntroduction
Bamboo data migration involves exporting all the settings from one instance to another. This is relatively easy, but can only be done in a bigbang approach; there's no way to export a single plan by itself. All build plans and other configuration including user-management data will
be included in the backup.

Backup
In the Source machine, the specific steps to follow to export the bamboo data are detailed in the Bamboo Installation
Guide#ExportOldBambooPlans, section 4.2.1. This will generate a zip file containing all the bamboo data, which you can then copy over to
the target machine for importing.

Taking a backup will make Bamboo temporarily unavailable

Bamboo in production is currently configured to take a backup daily. Restoring one of these backups is likely to be much faster and more

convenient than performing an out-of-band backup. You can find these backup at the path D:\devtools\Bamboo\home\backups

Restore
After copying the backup zip file across to the target server, follow the steps in the bamboo install guide, section 4.2.2. This will import the
zip file containing all of the source machine's bamboo configuration.

Post Restore Steps

After Importing the backup zip file, you will no longer be able to login to crowd even with a valid admin user, because bamboo will be
attempting to validate the user against the source machine's crowd instance which requires an SSL certificate to work properly. The steps to
resolve this and get bamboo back up and running are detailed in the bamboo install guide, section 4.2.3.
If you find yourself locked out, you can tell Bamboo to bypass Crowd and use local authentication instead. This will allow you to recreate the
Crowd connection, which may be necessary if you're restoring from Production to QA. To revert to local user auth, do the following:
E
E
E
E
E
E

Stop Bamboo
Go to the directory D:\devtools\Bamboo\home\xml-data\configuration
Copy the file "atlassian-user.xml"
Edit the file "atlassian-user.xml"
Replace the line <crowd name='Crowd Repository' key='crowd'/> <hibernatewith name="Hibernate Repository" key="hi
bernateRepository" description="Hibernate Repository" cache="true"/>
Start Bamboo

You should then be able to log into Bamboo with the username "localadmin" and the password "admin"
You can reset the local admin account by following these steps: https://confluence.atlassian.com/display/BAMBOO/Restoring+pas
swords+to+recover+admin+users

Bamboo Remote Agent Setup Proceedure

There are two types of Bamboo agents:
local agents run as part of the Bamboo server.
remote agents run on computers, other than the Bamboo server, that run the remote agent tool.
Local Agents
Local agents run on the Bamboo server and can use significant resources. If the server is constantly under resource pressure, then
it's ability to do this effectively is reduced, which will cause performance issues in the Bamboo server. Therefore, local agents
should not be used.
Before begin:
Do you have sufficient agent licenses? See Bamboo licensing for details.
Does your system meets the minimum requirements? See Supported platforms.
Do you have a supported version of Java installed on the agent machine? See Supported platforms.
Step 1. Enable remote agent support

E
E

1. Click the
icon and select Overview.
Click Agents (under 'Build Resources')
Click either Enable Remote Agent Support or Disable Remote Agent Support.

Step 2. Download and install the remote agent

E
E
E
E

1. Create a directory on the agent machine (e.g. bamboo-agent-home) to serve as the Bamboo agent home for the remote agent.
2. Click the
icon and select Overview.
Click Agents in the left panel (Under Build Resources). This will display the 'Agents' screen, showing lists of all local agents and al
remote agents that currently exist on your Bamboo system.
If not already enabled, click the Enable remote agent support link
Click Install Remote Agent. The 'Installing a remote agent' screen will display
Click DOWNLOAD Remote Agent JAR and save the JAR file to the directory on the agent machine that you created above.

Copy the command under 'Running a Remote Agent' to the clipboard for use in Step 3 that follow

Step 3. Launch the remote agent

Once installed, run the remote agent by executing the command line obtained above. This command will look something like this:
java -jar atlassian-bamboo-agent-installer-X.X.X.jar https://bamboo.service.dev/agentServer/

Where X.X.X represents the Bamboo version number.

The name of the jar file, for example, atlassian-bamboo-agent-installer-5.4-SNAPSHOT.jar, will vary depending on the version of
Bamboo you are running.

You can run the remote agent with a number of additional command line parameters. Configuration options include remote agent data
storage, capability detection and logging, suppression of self-signed certificate and running without the Remote Agent Supervisor or with
different start-up commands.
See Additional remote agent options for more information.
Step 4. Configure the remote agent's capabilities

All remote agents feature a capability that can be defined. Examples include an executable, such as Maven, a JDK, a DVCS client or a
custom capability. They typically define the path to an executable that has already been installed, and must be defined in Bamboo before
Bamboo or its agents can make use of them.
Capabilities can be defined specifically for an agent, or shared between all local or all remote agents.
Please see Configuring capabilities for more on defining capabilities.

Bamboo Space Management - Configuring build results expiry for a plan

By enabling build expiry for just a plan (described below), one can override the global expiry settings that affect all plans. If build expiry for a
plan is disabled, that plan's build result data will never be automatically deleted from the Bamboo server.
One can choose the build result data that will be kept for a plan and for how long this data will be kept (e.g. for reporting purposes), before
Bamboo automatically deletes it.
The results of a plan build can also be deleted manually.

Configuring the expiry of build results for a plan

Before begin:
Ensure to back up the build results data before its expiry date is reached.
To enable and configure the expiry of build result data for a particular plan:
E
E

Navigate to the configuration for the desired plan, as described on Configuring plans.
Click Miscellaneous to display the plan's current build expiry settings.

E
E

Select the Override global build expiry configuration check box. The following fields will be displayed:
Click Save.

Setting

Result

Minimum
builds to
keep

Specifies the minimum number of build results you want to keep.

E.g. specify '50' to keep the latest 50 build results, even if they are older than the period specified withExpiry period.

Labels to
keep

Specifies the build labels (not plan labels or job labels) applied to builds for which you want to keep build results, regardless

Expiry
period

Specifies the period (days, weeks or months) for which you want to keep build results.
E.g. specify '24 months' to keep all build results for the last two years.

Build
results

All build results data (including artifacts and build logs) are deleted.

of the Expiry period and Minimum builds to keep settings. Note that builds can be labelled
eithermanually or automatically.

Build logs Only build logs are deleted from the build results.

Artifacts

Only user-defined artifacts are deleted from the build results.

Note that the build expiry event is a global event that runs periodically, regardless of whether you disable or enable build expiry in
your plans. When this event occurs, the build results for your plan will be expired according to the criteria specified in the settings
above or globally. To configure the global event and global build expiry settings, please refer to Configuring global build results
expiry.

Screenshot: Enabling Build Expiry

Disabling the expiry of build results for a plan

To disable expiry of the build result data for a particular plan:

E
E
E
E

Navigate to the configuration for the desired plan, as described on Configuring plans.
Click Miscellaneous.
Select the Do not expire anything for this plan check box.
Click Save.

Screenshot: Disabling Build Expiry

Bamboo Upgrade to v5.6.1

Bamboo Upgrade
This document describes the steps taken to upgrade Bamboo from version 5.0 to version 5.6 in the QA environment. You will need the
following:
SQL Management Studio, with dbowner rights on the Bamboo database
Bamboo 5.6.1 zip file from Atlassian (downloaded to "D:\devtools\atlassian-bamboo-5.6.1.zip" on the Bamboo QA server)
Tomcat 7.0.55 for Windows x64
Local Admin access to the Bamboo server

Backup the database

E
E

Open SQL Management Studio and connect to the Bamboo DB

Verify you have the necessary permissions:
E
Expand Databases
E
Expand Bamboo
E
Expand Security
E
Expand Users
E
Double-click on your user
E
Click Membership
E
Confirm that "db_owner" is ticked:

E Right click the Bamboo database

E Select "Tasks" -> "Back up"
E Click "Remove" to remove the auto-named backup

E Click "Add"
E Give the backup a name you can easily remember

E
E

Click OK
Wait until you see the message "The backup of database 'bamboo' completed successfully"

Stop Bamboo
E
E
E
E
E
E

Log onto the Bamboo server

Stop the Bamboo service "Bamboo build server"
Open an elevated command prompt
CD to D:\devtools\Bamboo\install
Run "UninstallService.bat"
The script should return success

Install Bamboo
E
E
E
E
E
E
E
E

Extract the Bamboo 5.6 install to D:\devtools\bamboo-5.6.1

Add the Bamboo user (AUBambooDSA) to D:\devtools\bamboo-5.6.1 with full permissions
Open the file "D:\devtools\bamboo-5.6.1\atlassian-bamboo\WEB-INF\classes\bamboo-init.properties" in Notepad
Add the line "bamboo.home=D:/devtools/Bamboo/home" (note the slashes are forward slashes, not backslashes!)
Open an elevated command prompt
CD to "D:\devtools\bamboo-5.6.1"
Run "InstallAsService.bat"
Wait for confirmation that the operation succeeded:

Backup Bamboo configuration

E
E
E

E
E

Open an elevated command prompt

Using Windows Explorer, go to "D:\DevTools\Bamboo"
Right click the "home" folder and check the size (recommendation is to use Windirstat or similar), excluding the following folders:
E
Backups
E
Artifacts
E
Logs
If there is not enough space to copy everything but the above folders, you will need to free up some more space
Using the elevated command prompt, run the following command to backup the data: "robocopy D:\DevTools\Bamboo\home
D:\DevTools\Bamboo\bamboo_50_data /xd artifacts /xd backups /xd logs /E /XO"

Note: using Robocopy is much, much faster as there are lots of little files in the SVN caches. Windows Explorer does not copy these
efficiently

Configure listener

E
E
E

Copy the file "D:\devtools\Bamboo\install\conf\bambooKeyStore.jks" to "D:\devtools\Bamboo\keystore\bambooKeyStore.jks" (create

the keystore folder as necessary)
Open the file "D:\devtools\bamboo-5.6.1\conf\server.xml"
Comment out the Connector listening on port 8085 over HTTP

E
E
E
E
E

Uncomment the Connector listening on port 8443 over HTTPS

Change the port from 8443 to 443
Add a line "keystoreFile="D:\devtools\Bamboo\keystore\bambooKeyStore.jks"
Add a line "keystorePass=changeit"
Add a line "protocol="org.apache.coyote.http11.Http11Protocol""

Start Bamboo

E
E

E
E
E

E Download Tomcat 7.0.55 x64 for Windows zip. The Bamboo .zip file only contains the x86 version (file downloaded to
"D:\devtools\Softwares\apache-tomcat-7.0.55-windows-x64.zip" on Bamboo QA)
Extract Tomcat x64 to a temporary location
Overwrite the following files with those from the bin folder of x64 Tomcat in the temporary location:
E
D:\devtools\bamboo-5.6.1\bin\tcnative-1.dll
E
D:\devtools\bamboo-5.6.1\bin\tomcat7.exe
Remove the following files from D:\devtools\Bamboo\home\plugins if they exist:
E
agent-smith-wallboard-4.4.2.3.jar
E
bamboo-sonar-tasks-1.8.0.jar
E
bamboo-sonar-tasks-1.8.1.obr
E
bamboo-sonar-web-1.8.0.jar
E Download http://dl.bintray.com/jfrog/jfrog-jars/org/jfrog/bamboo/bamboo-artifactory-plugin/1.7.4/bamboo-artifactory-plugin-1.7.4.jar (it
s 18.7MB)
Copy this plugin to D:\devtools\bamboo-5.6.1\atlassian-bamboo\WEB-INF\lib
Remove any other bamboo-artifactory-plugin-*.jar files
Start the Bamboo service
E Using cmtrace.exe (available in C:\Windows\cmtrace.exe on the Bamboo QA server) monitor the upgrade logs:
D:\devtools\bamboo-5.6.1\logs
E Once you see the line "[StrutsSpringObjectFactory] Struts-Spring integration initialised successfully" in the stdout.log, try to logon
and validate the upgrade

Application links

E
E
E
E
E
E
E
E

Go to the Administration settings and then Application links

Delete the Jira application link from Bamboo
Log onto Jira. Delete the Bamboo link from Jira
Back in Bamboo, create the Jira link. Do not select the option to go to Jira
In Jira, add the application link for Bamboo
Once both application links have been created, go back to Bamboo and enable incoming and outgoing OAuth
Refresh Jira and click 'configure' on the Bamboo application link. Clicking the OAuth tabs should show OAuth has been configured
both directions
Repeat steps 2 7 for Confluence

Figure 1 Jira 5

Figure 2 Bamboo

Rollback Plan
E
E
E
E
E
E
E
E
E
E

Stop the Bamboo service

Open an elevated command prompt
CD to D:\devtools\bamboo-5.6.1
Run UninstallService.bat. It should complete successfully
Refresh services.msc to confirm the service has gone
CD to D:\devtools\Bamboo\install
Run InstallAsService.bat. It should complete successfully
Refresh services.msc to confirm the service has appeared
Modify the service to use AUBambooDSA as the logon account
Restore the database using SQL Management Studio

From the backup directory D:\DevTools\Bamboo\bamboo_50_data copy and overwrite the following into D:\DevTools\Bamboo\home:

E
E
E

E
Xml-data\configuration*
E
Bamboo.cfg.xml
E
Bamboo-mail.cfg.xml
Start the Bamboo service
Monitor the log file "C:\Users\AUBamboodsa\bamboo.log" and ensure Bamboo starts back up correctly
Validate you can log into the Bamboo web interface

Bamboo remote agent setup for version 5.6.3

Introduction
A Bamboo Remote Agent is a piece of software that is installed on a box to be used for bamboo builds or deployments

Bamboo guide
Basically it involves downloading a jar file and running a command on the remote agent box.
To install a remote agent, please follow these instructions:
E
E

Ensure that you have Java Runtime Environment 5.0 or later installed on the agent machine.
Download the remote agent JAR file to a directory on the agent machine/ Copy the files from the below location:

\\svrau055csm01\AISUploads\Developement Tool Set\Bamboo\Remote Agent\

Install instruction can be found at https://bamboo.service.dev/admin/agent/addRemoteAgent.action (QA box ) /

https://confluence.atlassian.c om/display/BAMBOO044/Bamboo+remote+agent+installation+guide
Install command with no ssl check
Prod

java -Dbamboo.agent.ignoreServerCertName=true -jar

atlassian-bamboo-agent-installer-5.6.3jar https://bamboo.service.abc/agentServer/

Dev

java -Dbamboo.agent.ignoreServerCertName=true -jar

atlassian-bamboo-agent-installer-5.6.3jar https://bamboo.service.dev/agentServer/

Install command with no ssl check and in a new directory. (Default is "bamboo-agent-home")
Prod

java -Dbamboo.agent.ignoreServerCertName=true -Dbamboo.home=/<directory path> -jar

atlassian-bamboo-agent-installer-5.6.3.jar https://bamboo.service.abc/agentServer/

Dev

java -Dbamboo.agent.ignoreServerCertName=true -Dbamboo.home=/<directory path> -jar

atlassian-bamboo-agent-installer-5.6.3.jar https://bamboo.service.dev/agentServer/

Note: Make sure that the directory is already created.

Bamboo agent IBM java
Install command

java -jar atlassian-bamboo-agent-installer-5.6.3.jar

https://bamboo.service.abc/agentServer/

The installation will be terminated with error. Please follow the below steps to restart the agent
Post install an number of config setting need set as well as trustedkeystore containing bamboo cert chain.
Edit the wrapper config file conf/wrapper.conf and add the following line to the config file in the correct order
Tells java where to find the ibm security libs ( Add these 2 lines only if you are getting IBM Java error)

wrapper.java.classpath.3=/app/WebSphere/AppServerV85/plugins/com.ibm.ws.security.cr
ypto.jar
wrapper.java.classpath.4=/app/WebSphere/AppServerV85/plugins/com.ibm.ffdc.jar

Tells java what trusted store to use and password (Mandatory)

Note: Copy the bambooKeyStore.jks keystore from the path "\\svrau055csm01\AISUploads\Developement Tool Set\Bamboo\Remote
Agent" to the agent box.
Point wrapper.java.additional.3 to keystore path and update password field as required in the wrapper config file conf/wrapper.conf

wrapper.java.additional.3=-Djavax.net.ssl.trustStore=<path>/bambooKeyStore.jks
wrapper.java.additional.4=-Djavax.net.ssl.trustStorePassword=<password>

Please supply the password as provided by the Bamboo admin.

Restart the agent

After the above steps are completed, restart the agent by running the below command:
Path:/<installation folder>

Rerun agent
bamboo-agent.sh start

Approve agent access

Go to the below path and approve the agent waiting for approval:
https://bamboo.service.abc/admin/agent/viewAgents.action

Additional Steps:
E
E
E
E

Take a backup of ${JAVA_HOME}/jre/lib/security/cacerts

Add the cacerts provided by tools team.
Add the following to wrapper.conf wrapper.java.additional.5=-Djavax.net.ssl.trustStore=/home/sandusr1/bambooagent-home/tools-cert/bambooKeyStore.jk
Export MAVEN_OPTS to the following
-Xmx512m -XX:MaxPermSize=256m
-Xss2m
-Djavax.net.ssl.trustStore=/home/sandusr1/bamboo-agent-home/tools-cert/bambooKeyStore.jks
-Djavax.net.ssl.trustStorePassword=changeit -Djavax.net.ssl.keyStore=/home/sandusr1/bamboo-agent-home/toolscert/bambooKeyStore.jks -Djavax.net.ssl.keyStoreType=jks -Djavax.net.ssl.keyStorePassword=changeit
-Dmaven.wagon.http.ssl.insecure=true -Dmaven.wagon.http.ssl.allowall=true