From your brief description, I assume you have configured some form of Repository trigger in your plan and Bamboo fails to trigger a new build based on your changes in the repository - thereby resulting in code coverage not getting completed. Correct me if I understood it wrong.
If the repository is in Bitbucket server, we should be able to see something like this in atlassian-bamboo.log:
If you don't see this, you would have to contact Atlassian Support to confirm if the issue is with connectivity or with Bamboo performance.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot