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
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
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 !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This also happens on a repository I created today. No branches, no PRs, just the pipelines. Are there other triggers for this issue?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Celeste Garcia I am not aware of anything else that causes this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
:( darn . .. ..
it's okay, thanks for the swift response
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.