Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Plan showing old directory after export/import

I have a current bamboo instance on  I exported all my data from the instance, installed a new instance on 5.14.5 and then imported the exported data.  I then updated to the latest version of bamboo.  So I currently have my original instance in one folder and my new instance with the latest version.  When trying to build a plan that builds successfully in the original instance, I run into an error where environment variable is using the home path of the original instance.  My original instance was located in C:\BuildServer my new instance is located at C:\BuildServer 2018.  Once of my steps uses an environment variable that looks like this "Mobile=${}\" this is used in the postbuild step for MSBuild.  However, when that step runs instead of being C:\BuildServer 2018\***** it is C:\BuildServer\*****  The only thing I can think of is that it kept information from the import and is using the old environment parameter.  Any help would be greatly appreciated.

1 answer

0 votes
Gabriel Ribeiro
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Sep 06, 2018

Hi Carlos,

Could you please open the C:\BuildServer 2018\bamboo.cfg.xml file and double check if the following parameter is set using the ${bambooHome} variable?

<property name="buildWorkingDir">${bambooHome}/xml-data/build-dir</property>

Not only this one but all other paths should be set using this variable.

Here is my config file for you to compare:

<?xml version="1.0" encoding="UTF-8"?>

<property name="">${bambooHome}/artifacts</property>
<property name="">${bambooHome}/xml-data/configuration</property>
<property name="">failover:(tcp://bamboo:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&amp;maxReconnectAttempts=10</property>
<property name="">nio://</property>
<property name="">${bambooHome}/xml-data/builds</property>
<property name="">${bambooHome}/xml-data/repository-specs</property>
<property name="buildWorkingDir">${bambooHome}/xml-data/build-dir</property>
<property name="hibernate.c3p0.acquire_increment">3</property>
<property name="hibernate.c3p0.idle_test_period">30</property>
<property name="hibernate.c3p0.max_size">100</property>
<property name="hibernate.c3p0.max_statements">0</property>
<property name="hibernate.c3p0.min_size">3</property>
<property name="hibernate.c3p0.timeout">120</property>
<property name="hibernate.connection.driver_class">org.postgresql.Driver</property>
<property name="hibernate.connection.password">PASSWORD</property>
<property name="hibernate.connection.url">jdbc:postgresql://postgres:5432/bamboo</property>
<property name="hibernate.connection.username">bamboo</property>
<property name="hibernate.dialect">org.hibernate.dialect.PostgreSQL82Dialect</property>
<property name="hibernate.setup">true</property>
<property name="license.string">license String - Sanitized</property>
<property name="lucene.index.dir">${bambooHome}/index</property>
<property name="serverId">0000-0000-0000-000</property>
<property name="serverKey">366</property>
<property name="webwork.multipart.saveDir">${bambooHome}/temp</property>


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events