Hi, We have a CI environment that is on a network with limited bandwidth. This is being fixed but will take a little longer. We set the bamboo build repository settings to not do a clean build to improve the time since 1 of our repos is 3gb big. With the source code repo set to not clean, we still have times where it does do a full clean as shown below.
How can I prevent this? Would caching the repo on remote agents help this performance?
Any other suggestions other than the obvious of getting the network bandwidth fixed.
Thanks in advance
simple 09-Apr-2018 18:34:28 Updating source code to revision: 04bdcea37c7ca108a81cf4359b2f13903df6fe29 simple 09-Apr-2018 18:34:30 Fetching 'refs/heads/BranchName1' from 'https://github.com/Company/CompanyWeb.Net.git'. Will try to do a shallow fetch. simple 09-Apr-2018 18:34:33 From https://github.com/Company/CompanyWeb.Net simple 09-Apr-2018 18:34:33 + c44b08256c...1573aa7408 BranchName1 -> BranchName1 (forced update) simple 09-Apr-2018 18:34:33 Checking out revision 04bdcea37c7ca108a81cf4359b2f13903df6fe29. simple 09-Apr-2018 18:34:33 fatal: reference is not a tree: 04bdcea37c7ca108a81cf4359b2f13903df6fe29 error 09-Apr-2018 18:34:33 Checkout to revision 04bdcea37c7ca108a81cf4359b2f13903df6fe29 has failed. simple 09-Apr-2018 18:34:33 Warning: failed to checkout source code to directory 'E:\bamboo-agent-home\xml-data\build-dir\LS-OWAPI-JOB1', trying to recover... simple 09-Apr-2018 18:34:48 Cleaned source directory 'E:\bamboo-agent-home\xml-data\build-dir\LS-OWAPI-JOB1'... simple 09-Apr-2018 18:34:48 Creating local git repository in 'E:\bamboo-agent-home\xml-data\build-dir\LS-OWAPI-JOB1\.git'. simple 09-Apr-2018 18:34:48 Initialized empty Git repository in E:/bamboo-agent-home/xml-data/build-dir/LS-OWAPI-JOB1/.git/ simple 09-Apr-2018 18:34:49 Fetching 'refs/heads/BranchName1' from 'https://github.com/Company/CompanyWeb.Net.git'.
Can you try disabling Use shallow clone in the respective linked repository? (And clear fit cache under *Overview -> Repository settings*)
It appears like the checkout of a specific revision is failing and I suspect it could be due to the shallow clone with depth=1 because the checkout seem to happen when it is cloned fully subsequently.
You can try cloning outside Bamboo via command line and see if you can reproduce this issue.
That said, enabling repository caching on agent will definitely help. (found under Git Repository's advanced options) This creates a full clone of the repository in agent directory fit the first time. All remote updates go into that repository and because that repository is not destroyed between builds, Bamboo does the checkout from that repository into the build working dir. So, even if you need clean checkout, it should be quite fast.
Hope that helps.
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events