Dynamic Pipeline Runners

[Scott Klein]

I have just started using self hosted runners for our project on my laptop, but that is not our end goal.

We would like to use AWS ECS to host our runner(s), however that leads to 1 important question:

Can we register dynamic instances of a runner automatically?

AWS ECS will spin up a new container when it needs one and that would have to be a new and unique runner registered in our repo. Currently, this is all done manually via the Repository Settings > Pipelines > Runners page and you have to execute a custom docker command on the machine hosting the runner.

What part of that command is actually unique to each individual runner, and would I be able to script that so that Bitbucket will recognize it and register it as an available runner for my repo?

[Syahrul · Accepted solution]

Hi @Scott Klein

We do have an existing conversation on this at the following community thread:

• Possibility of Spawning Dynamic Runners? 

We are planning to release the APIs so that you can build a custom solution to automate the creation of the runners.

We also have an existing feature request on this that I highly suggest you Vote and Watch so that you'll receive an update whenever we have any at:

• https://jira.atlassian.com/browse/BCLOUD-21343

I hope this helps!

Cheers,
Syahrul