Can multiple plans share a common 3rd-party directory
Usage FAQ
- Can multiple plans share a common 3rd-party directory
- Changing Bamboo database settings
- 複数のアトラシアンアプリケーションを単一の Tomcat コンテナーにデプロイする
- 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 connect Bamboo to an unsupported database
- 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
- Monitoring and Profiling 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
このページの内容
関連コンテンツ
- 関連コンテンツがありません
For example, you might have three repository directories, say, A, B, and C, where A is a common 3rd-party library. A is used across projects.
At this stage, Bamboo doesn't support having multiple checkout directories per build plan. However, you can work around this by setting these three directories up as separate Bamboo build plans - P A, P B and P C.
To make this work, you will also need to specify as an argument to your build scripts for P B and P C the location of A, which will be something like this:
../Plan_key_for_A/
Using a set up like this, your library module (A) should only be checked out once across the Bamboo instance.
最終更新日 2012 年 5 月 5 日
関連コンテンツ
- 関連コンテンツがありません
Powered by Confluence and Scroll Viewport.