Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,552,631
Community Members
 
Community Events
184
Community Groups

Bamboo plan does not start

김세희
김세희 Nov 14, 2018

Hello.

I currently use Bamboo 5.7.2 as a CD. I operated the bamboos in their usual configuration.
But it doesn't work and only the message ' Build: #59 has been queued for 1429 minutes' was received.
All plans work like that without an error message. I stopped all configurations and ran 'Source Code Checkout' but the result was the same.
I think that is a Git problem. Is there a solution?

Answer
Watch
Like Be the first to like this
954 views

1 answer

0 votes
Daniel Santos
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 23, 2018 • edited

Hello.

Usually this problem happens when there is no agent to process the specified build.
Since this problem is happening with multiple plans I would try:

  1. Check if your agents are available.
  2. If they are online, verify if they are dedicated. It could prevent other plans from using it.
  3. If this is a problem with GIT, other plans with SVN or a different repository would work. Do you have plans with Mercurial, SVN or CVS? Are they working as expected?
  4. In case you confirm is GIT, please check if the capabilities are configured as expected. Check if any recent change was performed in the GIT installation recently.
Reply

Suggest an answer

Log in or Sign up to answer
Bamboo
Bamboo
TAGS
AUG Leaders

Atlassian Community Events

See all events