Self-hosted runners set up in bulk

[Radu Cristescu]

I can't see a way to do it, but fingers crossed I missed something.

Is there a way to easily make 32 repositories use my self-hosted runners without going through each and every step of each and every repository to add `runs-on`? Because if I have to do that grunt work, I'm already considering using Jenkins and webhooks instead of Bitbucket Pipelines.

I'd be happy with a script that can add the `runs-on` automatically for me, while also aware of YAML anchors so it doesn't add it at merge points and just to definitions.

[Syahrul]

G'day, @Radu Cristescu 

I believe what you are looking for is a Dynamic pipeline this feature will allow you to enforce pipeline builds to be run on runner self-hosted rather than having to update each of the repositories in your workspace.

Regards,
Syahrul

[Radu Cristescu]

Ha... I totally missed those. "Ensure execution on Self-hosted runners" is on the short list of examples.

And just below: "standardised and reusable ‘blocks’ of CI/CD workflows".

It might be just what I need. I'll investigate further. It should be way better than mass repo edits or uprooting everything and moving to Jenkins or another platform.

Thank you

[Radu Cristescu]

@SyahrulRegarding Forge apps (private, unpublished): do they have to be owned by me and use my own API token?

What happens if the owner's account disappears because "just won the lottery and quit"?