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 Sign up to answer
Community showcase
Asked Dec 06, 2018 in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

5,535 views 21 17
View question

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