Bamboo doesn't run a build instance

Although I have set the ec2-instance and Bamboo is triggering new Windows instance based image that should 

run it - it's doesn't run on this instance.

Please advise,

Build result summary

Details

AgentNo agents are available to build this job. this job can be run on an elastic agent by starting a new elastic instance.Queued

Revision236cfa741466185c4f3fc0610d1b30c5707b728b 

2 answers

1 accepted

Accepted Answer
1 vote

Hello Yossish,

Thank you for your question.

We suspect you might be experiencing this bug which suggest starting up the agent manually.

If you also agree, I would suggest on adding any comments to the issue above as well as voting on the issue to create its popularity and likelihood of being fixed in a future release.

Please see the document below for more information on Atlassian's bug fixing policy.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

Kind regards,
Rafael P. Sperafico
Atlassian Support

Yet, this is not the only issue.

 

I can't find a linux instance also to run it.

 

Ubunto doesn't work and anothe amazon instance doesn't do the job as well.

 

Yossi

 

Apr 16, 2015 9:10:24 AM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.
Apr 16, 2015 9:10:25 AM Requested that new elastic instance be created for configuration: Ubuntu stock image / ami-fac5f7e7
Apr 16, 2015 9:10:25 AM Detected that a pending instance request for image [Ubuntu stock image], ami: ami-fac5f7e7 has been abandoned.
Apr 16, 2015 9:13:19 AM Requested that new elastic instance be created for configuration: Ubuntu stock image / ami-fac5f7e7
Apr 16, 2015 9:13:19 AM Detected that a pending instance request for image [Ubuntu stock image], ami: ami-fac5f7e7 has been abandoned.
Apr 16, 2015 9:16:47 AM Requested that new elastic instance be created for configuration: Amazon-Image / ami-04003319
Apr 16, 2015 9:16:47 AM Elastic instance [i-29f046e8] transitioned from STARTING to IDENTIFIED.
Apr 16, 2015 9:17:28 AM Elastic instance [i-29f046e8] transitioned from IDENTIFIED to RUNNING.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 7 hours ago in Jira Ops

Jira Ops Early Access Program Update #2: Let’s talk severity levels

Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...

19 views 0 0
Read article

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