I am evaluating Bamboo as a CI/CD option for my company, and I've run into a couple little snags.
When I spin up an instance of an elastic image, such as 'Ubuntu stock image' or 'Amazon Linux stock image', the Elastic Agent that it runs always has "No builds can be executed. The capabilities may not meet the requirements for any jobs or the agent may be dedicated to specific deployments." The actual elastic image, and the elastic instance itself do not have that message, in fact they correctly show that they can run my jobs, and the Agent Matrix correctly shows that they can run the jobs/plan that I had set up.
I have a secondary issue which I am not sure is related. I have my repository in BitBucket and I set it up to use the Bamboo hook so it can push changes to my Plan Branch, using my credentials. I also configured the Plan Source Repository settings to look at the proper repository, with all the proper credential values. However, when I push commits to a branch on BitBucket, it does not trigger the build plan for the branch. I can manually run the build and it does get the proper commit, and it even runs on the agent which says it can't run any jobs. I'm very confused here, and the online docs didn't really help.
I managed to get my BitBucket repo to successfully tell Bamboo to run the plan branch upon pushing new code to a feature branch. Steps I took:
Still no explanation for why the Elastic Agents say they can't run any jobs even though they do...
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
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