I've got Bamboo picking up github commits and starting up an elastic instance of an EC2 AMI image.
On the build queue I can see my job, but it says that "No agent can build this job".
When I click the lightning-flash to manage elastic instances I can see an instance running, but the elastic agent is "pending".
When I look at the job/plan there are no unmet requirements, but it says it can be built on No Agents / 1 elastic image.
So I assume I need to set up an agent. The docs at https://confluence.atlassian.com/display/AOD/Viewing+your+elastic+agents say there should be an Agents link in the left panel of the Bamboo Overview page, but I don't have one. Are there some other pre-reqs I haven't set up? How do I set up an agent to run on my elastic instance?
OK, so I realised I need an agent on my EC2 machine. I followed advice at https://confluence.atlassian.com/display/BAMBOO/Creating+a+custom+elastic+image+-+Windows to get that going. Tested it on-box and then manually starting from Bamboo. All good - I can spin up the instance OK.
Then I set up a trigger for a github repo change to build using the AMI I have made. When ti runs it spins up the AMI on EC2 as it should, but leaves the build status in Bamboo saying "No agent can build this job". All I'm trying to do is MSBuild the solution... and the Agents Matrix shows that the requirements are met by my AMI.
Does anybody know what I need to do next to invoke MSBuild on the .sln?
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs