I couldn't build my plan for Windows platform using Bamboo-cloud these days.

Hello there,

 

I couldn't build my plan for Windows platform using Bamboo-Cloud even if the same setting can build using my private Bamboo server using Elastic EC2 instances and it had been available to built using Bamboo-Cloud until last fall. The plan's jobs have just been queued and repeat turning on or off Elastic EC2 instances all day.

 

Here is the plan log running on my private Bamboo. It runs well.

Jan 7, 2016 6:29:23 AM Currently there are no agents that can build: AXUMF-AXUMF-JOB1. New elastic instance(s) will be started (providing the configuration allows it).

Jan 7, 2016 6:29:23 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.

Jan 7, 2016 6:29:23 AM Requested that new elastic instance be created for configuration: VcaSys - StockBurned / ami-afdc25c4

Jan 7, 2016 6:29:24 AM Elastic instance [i-ebde6058] transitioned from STARTING to IDENTIFIED.

Jan 7, 2016 6:30:24 AM Elastic instance [i-ebde6058] transitioned from IDENTIFIED to RUNNING.

Jan 7, 2016 6:37:33 AM An elastic agent is loading on instance: [i-ebde6058]

Jan 7, 2016 6:38:50 AM Elastic Agent "Elastic Agent on i-ebde6058" started on instance i-ebde6058

Jan 7, 2016 7:29:23 AM Elastic instance i-ebde6058 has been idle for longer than the configured timeout and will be shut down because the current paid hour is ending.

Jan 7, 2016 7:29:23 AM Elastic Agent "Elastic Agent on i-ebde6058" stopped on instance i-ebde6058

Jan 7, 2016 7:29:23 AM Requested termination of elastic instance: i-ebde6058

Jan 7, 2016 7:29:40 AM Elastic instance [i-ebde6058] transitioned from RUNNING to SHUTTING_DOWN.

Jan 7, 2016 7:30:20 AM Elastic instance [i-ebde6058] transitioned from SHUTTING_DOWN to TERMINATED.

Jan 7, 2016 7:30:20 AM Detected that the elastic instance [i-ebde6058] has been terminated.

 

But another plan on Bamboo-Cloud doesn't work properly. Here is the log.

Jan 14, 2016 9:20:18 AM Currently there are no agents that can build: AXUMF-AXUMF5-JOB1. New elastic instance(s) will be started (providing the configuration allows it).
Jan 14, 2016 9:20:18 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.
Jan 14, 2016 9:20:19 AM Requested that new elastic instance be created for configuration: Windows: AxUMF / ami-cc1373a4
Jan 14, 2016 9:20:20 AM Elastic instance [i-ccdb0245] transitioned from STARTING to IDENTIFIED.
Jan 14, 2016 9:21:00 AM Elastic instance [i-ccdb0245] transitioned from IDENTIFIED to RUNNING.
Jan 14, 2016 10:02:31 AM Elastic instance [i-ccdb0245] transitioned from RUNNING to SHUTTING_DOWN.
Jan 14, 2016 10:02:51 AM Elastic instance [i-ccdb0245] transitioned from SHUTTING_DOWN to TERMINATED.
Repeat ...

 

As you can see, there is no Elastic Agent messages. I expected these messages.

Jan 7, 2016 6:37:33 AM An elastic agent is loading on instance: [i-ebde6058]

Jan 7, 2016 6:38:50 AM Elastic Agent "Elastic Agent on i-ebde6058" started on instance i-ebde6058

Jan 7, 2016 7:29:23 AM Elastic instance i-ebde6058 has been idle for longer than the configured timeout and will be shut down because the current paid hour is ending.

Jan 7, 2016 7:29:23 AM Elastic Agent "Elastic Agent on i-ebde6058" stopped on instance i-ebde6058

Jan 7, 2016 7:29:23 AM Requested termination of elastic instance: i-ebde6058

 

I checked Windows Stock Images you provided show same result that there is no agent message.

 

I think that's why the job is just being queued all day.

Even if the plan says that it can be build using some Windows Images, it is just queued and can't be built saying there is no agents are available to build the job. The saying doesn't make sense.

 

I attached some screen shots. The instance logs have mixed status as I controlled instances for some test.

The ID of the problem job is AXUMF-AXUMF5-JOB1.

instances_log.pngjob_log.png

available_images.png

 

Bamboo-Cloud account is for my company. So I am so serious.

 

Please help me.

5 answers

This widget could not be displayed.

Hi, I'm facing the same problem as you...it's just not possible to get it running.
Do you have any solution ? Please help. 

This widget could not be displayed.

I am using the plan on my private Bamboo Server for a while as in my case the problem cause on the cloud service. I am looking forward to an Atlassian answer.

This widget could not be displayed.

Michal Sodomka I could make an image using the stock image(ami-33a6f959) of the latest Bamboo(5.10.0 build 51017) recently.

The bamboo agent works on the image. In my case, my custom image from the stock image run slowly and this problem seem to be another issue for me.

Anyhow you can try as I did. I hope you can get a good result.

This widget could not be displayed.

@Charles Lee, Atlassian Answers is not the place to resolve such type of issues. Better place to receive feedback from Atlassian is support.atlassian.com

This widget could not be displayed.

Alexey Chystoprudov, Thank you very much.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 11 hours ago in Jira

Atlassian Research Workshop opportunity on Sep. 28th in Austin, TX

We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...

32 views 1 2
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you