Hi Archie,
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:
POST <BITBUCKET_URL>/rest/remote-event-consumer/latest/events/stash-branch-changed-remote-event
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.