I’m wondering if using fly.io as Jenkins Agents (workers) is a good idea or not.
First I would need to implement a plugin similar to these:
- GitHub - jenkinsci/kubernetes-plugin: Jenkins plugin to run dynamic agents in a Kubernetes/Docker environment
- GitHub - jenkinsci/azure-vm-agents-plugin: This repo is for azure vm agents plugin for jenkins. Azure devops CICD is the team which owns it for now
This plugin would automatically manage the lifecycle of an agent (e.g. spin up a new fly.io instance for every new build).
Right now I use the kubernetes-plugin, and I have a few different images for different jenkins jobs.
My “problem” is that I have to wait for k8s to schedule a pod for me, which takes ~30sec. On top, if the pod scheduling happens to propagate to a new VM request from AWS (because the k8s cluster is full), then this time increases to 2-3 minutes.
If I read correctly this blog post: Docker without Docker · Fly, then this process of spinning up a new Jenkins Agent, could potentially be significantly faster. Right?
Also, is there any similar ongoing effort that I’m not aware of? Maybe for some platform other than Jenkins?
Thanks in advance