I have several projects which use a set of precompiled libraries. Our directory structure has this libraries folder at the same location as the base working directory of Bamboo. The libraries are also under version control and we are trying to figure out a way to have bamboo pull them to a directory that is not the working directory of the project being built.
edit: We are using mercurial
Since Bamboo 3.3 you can have your Source Checkout as a Task. You can have as many Tasks in any Job as you want. Tasks execute in sequence, inside the Job. Each Job runs on the same agent, inside the same build working directory.
* Task 1, Checkout the Libraries to subdir .\Libraries
* Task 2, Checkout Project A to subdir .\Project A
* Task 3, Build Project A using path references to .\Libraries that refer to the build.working.directory
A better solution, though, may be to look into Mercurial Nested repositories: http://mercurial.selenic.com/wiki/Subrepository?action=show&redirect=subrepos
I'm assuming developers will need to know which bits to checkout too and you don't want your CI builds building one way and your local Dev builds building a totally different way.
For how to reference a given build's working directory during the build, see: http://confluence.atlassian.com/display/BAMBOO/Using+Global%2C+Plan+or+Build-specific+Variables
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG