Dear Atlassian Support / Community,
We are writing to report an issue regarding the consumption of Atlassian-hosted build minutes, despite our configuration intending for all Bitbucket Pipelines to utilize our self-hosted autoscaler runners.
We have been using the atlassian/bitbucket-build-statistics tool to monitor usage. Initially, several repositories, including repository_one and repository_two, showed significant "Build Minutes Used" on Atlassian's infrastructure (approximately 23 hours and 19 hours, respectively, during the analyzed period).
Update: We have since identified and corrected a configuration error in the bitbucket-pipelines.yml for repository_one, which has resolved the issue for that repository.
However, the problem persists for repository_two. Despite a thorough review of its bitbucket-pipelines.yml file, the runs-on tags appear to be correctly configured to target our self-hosted runners. Nevertheless, this repository continues to accumulate Atlassian-hosted build minutes.
Could you provide insight into potential reasons why repository_two might still be consuming Atlassian-hosted runner minutes when its configuration appears correct? Furthermore, what methods can we employ to precisely identify which specific pipeline executions or steps within this repository are utilizing Atlassian's infrastructure?
Thank you for your assistance.
Sincerely,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.