Bamboo build stuck on "Waiting to be built..." and Cloning into 'Common'

Question

For some reason my bamboo build which uses MSBuild is stuck for past 4 hours with message below:

"Waiting to be built...".

I tried stopping the build but stuck on 'Cancelling....'. Can't even disable the Agent. Weird thing is there are 2 build agents in IDLE.

Before I stopped build, the build was running over 5 hours and did not stop. The log said:

simple  04-Mar-2015 21:23:42   Submodule 'web-common' (http://bitbucket.org/abc/web-common) registered for path 'Common'
simple  04-Mar-2015 21:23:43   Cloning into 'Common'...

Rebooted build server. Works for a few hours and same issue starts again. Sick of restarting a build server without knowing the ROOT CAUSE.

I'm quiet new to Bamboo and GIT. If you could help with advise on troubleshooting and fixing this issue will be good.

UPDATE:

I passed the build but getting error below for web deploy: C:\bamboo-home\artifacts\XXX\shared\build-xxxx\package is not a directory

Answer 1

It was password issue for submodule which is fixed.
Now I'm getting this error

Failure in artifact preparation phase during processing of: 
Subscription for Shared artifact: 
[bla, pattern: [**] anchored at: [deploy_artifact], destination: [] –  

Log message

"C:\bamboo-home\artifacts\XXX\shared\build-xxxx\package is not a directory" 

You can look at this thread:

Did you created a new deployment release after building your plan?
Single release always relates to specific build.
If you want to use updated artifact you need to create a new release.

You can also check copy pattern, as suggested here.

---

(Original answer)

Bamboo supports submodules since 3.4 and BAM 8106

If that support is somehow faulty, you can try a workaround, adding a builder task like a custom command executable as a script with:

#!/bin/bash
BUILDDIR=${bamboo.build.working.directory}
cd $BUILDDIR
git submodule update --init

(unselect the "Use Submodule" option in the Advanced Option)

That would allow you to check if submodules are actually the issue here.

Answer 2

Are you sure you have a running elastic instances ? I had a similar message and my build was queued for long time because I hadn't any running instances which Bamboo can use for building.