In my case bitbucket APIs are not so useful to deregister runners.
I have a repo and multiple steps in repo are using selfhost docker runner label and running simultaneosly in different vms using vm azure scale set.
vm get spinned up only when job runs and should get deleted once job completes and docker runner self drains.
Since docker runner does not self exits it is bit hard to watch out pipelines and go to scaleset and shut down vms
Kindly assist
Regards,
Arun
Welcome to the community.
Could you confirm if you're using Bitbucket Cloud Pipelines autoscaler?
If not yet, Pipelines autoscaler has an autoscaler cleaner where it automatically clean (delete) unhealthy runners and linked jobs.
If you're not using it, you will have to manually remove the stale runners and/or write your own script that will do the cleanup in your specific environment.
Regards,
Mark C
Thank you for your response @Mark C
I found a way to clean up
I am facing different issue now
Can I use same runner which is running in multiple VMs with same runner uuid and with same label
so can I run it in different steps of pipeline or different repo pipelines ?
I would like run all those steps or repo pipelines simultaneously without being queued
when I did so it throws an error
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.