Why does Bamboo wait to start a build when commanded manually?

Question

Hello,

Using the latest bamboo on Windows Server 2012 R2 - all working great.  5 agents setup, powerful server with multi-procs and 128 GB RAM.  When I click the play button to command a build, I see it show three dots ... and I have to wait somethings several minutes for the build to start.  Nothing else is in progress.  Why is there a delay and how can I have this fire immediately or more efficiently?

Thank you.

Pawel Skierczynski · Answer

Quiet period is not connected to manual build in any way. Nevertheless I would strongly discourage using quiet period feature. It will have performance problems with anything bigger than very small instance. Shallow clones will not help with change detection much.
SQL Server requires specific configuration. I hope you've seen this https://confluence.atlassian.com/bamboo/microsoft-sql-server-289276827.html.

Try running git clone manually on server to see how long doest it take.
Also check what git implementation does server use?
If using native git (recommended) setting logs to debug on com.atlassian.bamboo.plugins.git could tell us more (like if git fetch command is called early and just very slow). Logs can be tuned runtime from system admin menu.

Neal Culiner · Answer

I do have quiet periods on the linked repositories, but there was no activity in the past 5 minutes on them which is their quiet period.  Even if no activity would a commanded build action still way a quiet period amount of time?  That may be the culprit.

Neal Culiner · Answer

Thank you for the reply @Pawel Skierczynski I am using Windows Server 2012 R2 against SQL Server 2014 STD with Git.  No large repo's, about 20 repo's in total, all set to use shallow clones, etc.