Missed Team ’24? Catch up on announcements here.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Plans are going in queue only in new created Bamboo DC with LTS 9.6

Abhishek Bebni April 17, 2024

I created new Bamboo DC with LTS 9.6 and I can see some remote agents are already running in online mods but still when I run any plan, plan is not running and going into queue only and showing message that none agent is in online mode. Please suggest how we can run any plan or make the remote agents online so that plan can be run in Bamboo DC.

 

Thanks & regards

Abhishek Bebni 

1 answer

1 vote
Anik Sengupta
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 17, 2024

Hi Abhishek,

Thanks for contacting Atlassian community .

Looks like after upgrading to Bamboo DC 9.6 the build plans are been queued for building for an extended duration and is not showing on the Build activity dashboard as queued. You have Agents capable of processing the build available but it remains queued for an excessive period.

A large delay between queueing and it appearing in the build queue suggests that the server-side change detection process is taking longer (see further down for more information on the build workflow). It's helpful to understand the basics of the Bamboo build plan workflow to understand where the issue might be when the symptoms present:

A build plan is triggered.
Plan changes status to queued.
Change detection happens on the server-side. This is where it will reach out to the repository to determine if there are any changes it needs for the build and is the most likely breakdown point when observing queued builds that aren't yet in the build queue.
Plan is then added to the build queue. This is when it shows up on the Build activity dashboard.
Server assigns an agent for it and sends an event to the agent.
Agent receives the event and starts building.

It's important to note that this behavior is normal however we've observed a few causes for abnormally long server-side change detection:

This has been described here - https://confluence.atlassian.com/bamkb/build-plan-queued-for-extended-duration-and-not-showing-on-build-activity-dashboard-as-queued-in-bamboo-834220865.html

Also please check on the agrnt dedication if the p;lan had few dedicated agents and if those agents are online ready to acceot the build.

Please note local agents have been removed from Bamboo 9.6 if you have any plans which were previously build in local agents you need to switch them to remote agents to make sure they have the right capabilities for building.

Thanks

Anik Sengupta

**please don't forget to Accept the answer if your query was answered**

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events