The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Runner error when sizing to 16x

Celeste Garcia
February 27, 2025

Hi,

I'm using a self-hosted pipeline runner and it works with all sizes except 16x. As per the docs I should be able to scale up to 16x using this setup, but I get a configuration error:

The size '16x' in your bitbucket-pipelines.yml file is outside the allowed range. Please specify one of '1x', '2x', '4x' or '8x'.

 

Please advise on what is wrong or how to diagnose this issue, I'm completely lost atm

2 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 4, 2025

Hi Celeste and welcome to the community!

Thank you for reporting this. Our engineering team deployed a fix for this yesterday, so 16x steps with a self-hosted runner should work now.

Could you give it a try when you have some time and let us know if the issue is resolved?

Kind regards,
Theodora

Celeste Garcia
March 4, 2025

hey there!

i tried the repro steps in two scenarios (repo with just the python template, scaled to 16x and a repository with gradle using an existing pipeline) and they both work, no need to reopen PRs or anything.

all is good and many thanks for the follow-up !

0 votes
Brant Schroeder
Community Champion
February 27, 2025

@Celeste Garcia Welcome to the Atlassian community

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.

Celeste Garcia
February 27, 2025

This also happens on a repository I created today. No branches, no PRs, just the pipelines. Are there other triggers for this issue?

Brant Schroeder
Community Champion
February 27, 2025

@Celeste Garcia I am not aware of anything else that causes this.

Celeste Garcia
February 27, 2025

:( darn . .. ..

it's okay, thanks for the swift response

Like Brant Schroeder likes this
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events