We're in the process of migrating from Subversion to Git and are running into some issues with Bamboo. I updated the "Source Repository" for a plan and change the "Plan Repository" (default one) to Git. However, as soon as I try running a build, the build stays queued forever. It's stuck right before the point where it would clone the repository.
I've tried using the read-only git:// URL, the https:// URL and git-ssh. I'm able to clone the repository locally as the user that runs Bamboo. I've also successfully change to Git on other repositories, however, this is the second repository that has run into this issue.
I've tried reverting the Plan back to Subversion and it's experiencing the same behaviour. It feels like this entire plan is busted :(
Any help would be greatly appreciated. Thank you.
All the best,
It's Bamboo 4.3.1 build 3400. It turns out that hitting the "stop all builds" on the build plan resolves the issue. The build "ends" and the "real" build starts> It continues to work afterwards. We haven't had this particular issue again.
We're having other issues with the branch based builds that we'll have to file an issue with Atlassian. Thanks.
I've come across the same issue. What I have found in my situation that a hang occurs while awaiting authentication via SSH (but bamboo won't tell you this).
My solution involved uploading the SSH key and passphrase. If you change the git repo, even just adding a prefix ssh:// try re-adding the ssh key and passphrase again.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot