Shared checkout?

I'm currently evaluating Bamboo for game development purposes. One of the big concerns I have is the artifact sharing and the speed & efficiency of it for deployment.

A full build of a game can run into several gig in size, and the idea of checking out and compiling code and sharing THE ENTIRE CHECKOUT as an artifact to the next stage feels really inefficient to me.

Is there something I'm missing for how to handle this? The general idea is that for a standard build we just want to compile and commit binaries, but a deployment needs additional steps that I'd like to have as a separate (and perhaps manually triggered) stage/job.

2 answers

0 votes

Do you need the full checkout in the subsequent stages? Maybe you could share just the binaries?

Yes, we do need the full checkout, because it contains all of the assets required to deploy the product.

0 votes

In Bamboo 5.6, you'll be able to dedicate agents to builds, in this way all jobs will run on the same agent and they could share the build directory.

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,072 views 0 5
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot