In Bamboo 3.0 it will be possible to configure Bamboo to pass artifacts from one job to another. This should solve the problem of trying to use an artifact after it is built in another build.

Bamboo 3.0 should be shipped in February 2011.

As mentioned previously, svn externals can also be used to make it work with Bamboo versions before 3.0.

Due to this I will resolve this issue.

Please add a comment here if I am misunderstanding something and passing artifacts between jobs does not help.

this is a pretty big issue for us. do you have any idea if a fix for this will make it into a release in the near future? My workaround in BAM-1369 might be a way to approach this problem.

Hi Michael,

Firstly, many thanks for supporting Bamboo.

Secondly, with regards to multiple repository locations - what I am thinking is that Bamboo will probably keep the folder name of your svn module. In your case, I am thinking that you will have a set up like this:

• Your instance can have one Bamboo Project - (we can give this a key, say.. PROJ - note that this is not the same as the 'native svn project names' - it's at a broader conceptual level)
• You then setup two Build Plans under this project - (TRUNK, and BRANCH).
• You then have two repository locations under each build plan: (MyProject1, and MyProject2).

Then, what the file structure probably looks like is something like this:
/xml-data/build-dir/PROJ-TRUNK/MyProject1
/xml-data/build-dir/PROJ-TRUNK/MyProject2
/xml-data/build-dir/PROJ-BRANCH/MyProject1
/xml-data/build-dir/PROJ-BRANCH/MyProject2

I believe a setup like this should be able to resolve the issue you are currently experiencing?

Regarding running multiple copies - unfortunately, a copy of the Bamboo license only entitles you to one instance of the software (please see http://www.atlassian.com/software/bamboo/pricing.jsp#commercial).

Lastly - with regards to the challenge you are currently facing - I would recommend that you give subversion externals (http://svnbook.red-bean.com/en/1.0/ch07s03.html) a try in the short term. As an example, you can create two new "empty" "projects" in subversion: e.g. project-trunk and project-branch. Within each, you can then specify MyProject1 and MyProject2 as "externals" - this has been an approach used by others to set up plans which required multiple repositories (please see BAM-882). The only drawback of this is fisheye integration, which currently will not work for the external modules.

I hope this has helped.

Regards,
Edwin

Please note, having different repository locations would NOT help because Bamboo still renames directories on us. I have to make symbolic links to map the directories so things work.

Is this going to be scheduled for a fix?

We bought a licensed copy of Bamboo. Does that allow us to run multiple copies of it? The only way I can think of, short term, to get around this is to have multiple versions of Bamboo running in different JBoss instances (or whatever, we just happen to throw it into the jboss app server) AND set the Bamboo home to be something different.

By the way, we just got our [paid] Bamboo license, if that makes any difference.

That would help some, but it would also be nice to not have to manually create all these symbolic links for the projects so that it can traverse and find its things easily.

I suppose we could fix that if we had Ivy publish its artifacts to a repository instead of fetching them locally....

Guys,

I've linked to the related issue.

I think this issue would be fixed if you can specify multiple, different repository definitions.

Cheers,

Mark C

Is it possible to specify a different build directory for each plan? maybe in a secret xml file