Bamboo assembly stuck on "Expectation to be built ..." and "Cloning" in "Common"

Question

For some reason, my bamboo assembly that uses MSBuild has stuck in the last 4 hours with the message below:

"Awaiting construction ...".

I tried to stop the build, but was stuck on " Cancel ....". Unable to disable agent. It is strange that there are 2 build agents in IDLE.

Before I stopped assembling, the assembly worked for more than 5 hours and did not stop. The magazine 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'... 

The build server rebooted. Work within a few hours and the same problem starts again. Bolshaya restarting the build server, not knowing the cause-effect relationship.

I am familiar with Bamboo and GIT. If you can help with troubleshooting advice and fixing this problem, that would be good.

UPDATE:

I passed the assembly, but got the error below for deploying on the Internet: C: \ bamboo-home \ artifacts \ XXX \ shared \ build-xxxx \ package is not a directory

Answer 1

This is a password problem for a submodule that has been fixed.
Now i get 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 watch this thread :

Did you create a new deployment version after creating your plan?
A single release always refers to a particular assembly.
If you want to use the updated artifact, you need to create a new version.

You can also check the copy template as suggested here .

---

(Original answer)

Bamboo supports submodules with 3.4 and BAM 8106

If this support is somehow wrong, you can try a workaround by adding a build task, such as a custom executable command as a script with:

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

(deselect "Use submodule" in the advanced option)

This will allow you to check if submodules really exist.

Answer 2

Are you sure you have elastic instances? I had a similar message and my assembly has been queued for a long time because I did not have any running instances that Bamboo could use to build.