Hi Antoine, Could you clarify what you mean by: > Given our current resource utilization on Github Actions, it seems that > even a non-auto-scaling setup could be useful.
I could interpret it in a couple of ways ... Thanks, Micah On Fri, Mar 13, 2020 at 7:36 AM Antoine Pitrou <anto...@python.org> wrote: > > Le 13/03/2020 à 01:45, Brian Hulette a écrit : > > * What kind of devops tooling would be appropriate to provision and > > manage the instances, scaling up and down based on need? > > * What CI/CD platform would be appropriate to dispatch work to the > > cloud nodes (taking into consideration the high costs of sysadmin, and > > seeking to minimize nodes sitting unused)? > > > > I looked into solutions for running CI/CD workers on GCP a (very) little > > bit and just wanted to shared some findings. > > Appveyor claims it can auto-scale GCE instances [1] but I don't think it > > would go beyond 5 concurrent "self-hosted" jobs [2]. Would that be a > > problem? > > BuildKite has documentation about running agents on a scalable GKE > cluster > > [3], but unfortunately no way to auto-scale based on the backlog. We > could > > maybe roll our own/contribute something based on their AWS scaler [4]. > > Given our current resource utilization on Github Actions, it seems that > even a non-auto-scaling setup could be useful. > > Regards > > Antoine. >
