Bitbucket Pipeline Cloud step size bug?

Bitwise DEVS
Contributor
July 13, 2024

We initially tried 4x step size in a parallel steps and it works, however after changing it back to 2x in an attempt to save build times and returning it once again to 4x due to realization that the build can no longer work with low spec environment. The step is now having error.

Screenshot 2024-07-13 at 8.15.33 PM.png

 


Configuration error

The size '4x' in your bitbucket-pipelines.yml file is outside the allowed range. Please specify either '1x' or '2x'.

 

I was able to rerun a 4x size step. Clearly this seems to be a bug.

1 answer

1 accepted

1 vote
Answer accepted
Bitwise DEVS
Contributor
July 13, 2024

This issue no longer happens after closing a PR and creating a new one. It seems that a push and merge on a branch with existing PR where it triggers a pipeline can cause the above issue.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events