Moving Bamboo-Home of an agent
Usage FAQ
- Can multiple plans share a common 3rd-party directory
- Changing Bamboo database settings
- Deploying Multiple Atlassian Applications in a Single Tomcat Container
- How Bamboo processes task arguments and passes them to OS shell
- Securing your repository connection
- Changing the remote agent heartbeat interval
- Cloning a Bamboo instance
- How do I shut down my elastic instances if I have restarted my Bamboo server
- How do I stop the Bamboo server from automatically configuring my remote agent's capabilities
- JUnit parsing in Bamboo
- Known issues with CVS in Bamboo
- Monitor Memory usage and Garbage Collection in Bamboo
- Moving Bamboo-Home of an agent
- Performing a thread dump
- Restoring passwords to recover admin users
- Send Errors to stderr - Script Builder in Visual Studio WinXP to build Solutions Files
- Using Bamboo with Clover
- Working with Java libraries
- Bamboo indicates that my Ant or Maven builds failed, even though they were successful
On this page
Related content
- Scope of automation rule showing project ID instead of name
- Actor permission error in automation execution log
- The Jira Cloud Migration Assistant fails to complete due to the error "We couldn't export Automation Rules"
- Receiving an error message stating 'Unknown Error' when attempting to publish an Automation Rule
- Unable to enable the automation rule which was imported post migration to Jira Cloud.
- Unable to add some system rules in Jira Automation
- Jira Data Center unable to import automation rules from Jira Cloud
- Delete Automation rules in Jira Cloud
To move an agent's Bamboo-Home -
- Move the Bamboo-Home of the agent, to the intended location.
Edit the <Bamboo-Agent-Home>/bamboo-agent.cfg.xml file, find the following line -
<buildWorkingDirectory>/YOUR_OLD_DIRECTORY/xml-data/build-dir</buildWorkingDirectory>
- Point the working directory to the new Bamboo-Home.
- Start your Agent with -Dbamboo.home=your_new_agent_home and point to your new Bamboo-Agent-Home.
Last modified on Nov 23, 2018
Related content
- Scope of automation rule showing project ID instead of name
- Actor permission error in automation execution log
- The Jira Cloud Migration Assistant fails to complete due to the error "We couldn't export Automation Rules"
- Receiving an error message stating 'Unknown Error' when attempting to publish an Automation Rule
- Unable to enable the automation rule which was imported post migration to Jira Cloud.
- Unable to add some system rules in Jira Automation
- Jira Data Center unable to import automation rules from Jira Cloud
- Delete Automation rules in Jira Cloud
Powered by Confluence and Scroll Viewport.