Inconsistent Build Failures Consuming Free Minutes on Atlassian CI/CD

Aumirah Dashboard

Over the past few days, I have noticed a recurring pattern where my builds fail consistently for 3-4 consecutive runs, without any changes being made to the code or configuration. These failures consume my free minutes unnecessarily. After these failed attempts, the build eventually succeeds on the 4th or 5th attempt without any adjustments, indicating that the failures are not due to errors on my end.

 

I am writing to escalate an issue I’ve encountered with the usage of my free 50 minutes account on Atlassian CI/CD, which is negatively impacting my workflow.

Over the past few days, I have noticed a recurring pattern where my builds fail consistently for 3-4 consecutive runs, without any changes being made to the code or configuration. These failures consume my free minutes unnecessarily. After these failed attempts, the build eventually succeeds on the 4th or 5th attempt without any adjustments, indicating that the failures are not due to errors on my end.

This issue is concerning as it seems to be an unnecessary depletion of my limited free build minutes. I rely on these free minutes to manage my development workflow, and this ongoing issue is both frustrating and inefficient. Here are the specific details of the problem:

• Pattern: 3-4 consecutive build failures, followed by a successful build on the next run without any changes being made.
• Impact: Significant consumption of free build minutes due to unnecessary failed runs.

Theodora Boudale

Hi and welcome to the community!

We need some additional information to understand what is happening:

1. Do the 3-4 failed builds and the 4th or 5th successful build all run on the same commit?
   Are they re-runs of the same first failed build?
   
   
2. Do the failed builds fail during Build setup or when one of the step's commands gets executed?
   
   
3. Can you please share the command that fails and (a) its output from a failed build and (b) its output from the final successful build on the same commit?
   
   Please make sure to sanitize private/sensitive data in the command and outputs, if any, before sharing here.
   
   
4. If you expand the Build setup of a failed and a successful build on the same commit, can you please check the Images used: section? Is the Docker image and hash of this image the same in the failed and successful builds?

Until we figure this out: if you have run out of build minutes and you have a Linux machine where you can run builds, you can also set up a Linux Docker runner to run Pipelines builds on this machine.

• https://support.atlassian.com/bitbucket-cloud/docs/runners/
• https://support.atlassian.com/bitbucket-cloud/docs/set-up-and-use-runners-for-linux/
• https://support.atlassian.com/bitbucket-cloud/docs/configure-your-runner-in-bitbucket-pipelines-yml/

Runners allow you to run builds in Pipelines on your own infrastructure. You can still see build logs on the Pipelines page of the repo and you won’t be charged for the build minutes used by your self-hosted runners. This means that you can run builds even when the 50 free minutes have been used.

Kind regards,
Theodora