if I use the Source Code Checkout task cloning the repository takes up to 9 minutes. Most of the time is spent in these steps
01:43:17 Fetching 'refs/heads/*' from 'ssh://email@example.com:7999/ma/mybranch.git'.
01:43:17 Warning: Permanently added '[127.0.0.1]:36431' (RSA) to the list of known hosts.
01:51:55 From ssh://127.0.0.1:36431/ma/mybranch
01:51:55 * [new branch] mybranch
During this time the CPU load of the agent running on an AWS EC2 machine (c4.4xlarge) goes up to 100% using only one of the available 8 cores.
If I use a Script task to execute
git init myproject
git remote add origin ssh://firstname.lastname@example.org:7999/ma/myproject.git
cloning is much faster
14:48:59 Initialized empty Git repository in /root/bamboo-agent-home/xml-data/build-dir/MY-PROJ-JOB1/myproject/.git/
14:48:59 Warning: Permanently added '[stash.intapps.it]:7999,[10.130.14.156]:7999' (RSA) to the list of known hosts.
14:49:47 From ssh://stash.intapps.it:7999/ma/myproject
14:49:47 * [new branch] mybranch
What is causing this high load and how can I make cloning repositories faster?
this could be hard to pinpoint from the outside/from Community so I am only able to share some more generic information - the first attempt for diagnosing performance issues could be to follow the troubleshooting guideline.
In case the issue is still current and you have not reviewed the information recorded here, it could give a first clue:
Hi, If you are running self-managed environments and looking to adopt modern infrastructure, Bamboo Data Center can now be deployed in a Kubernetes cluster. By leveraging Kubernetes, you can easily...
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