smulc

Note from https://github.com/orgs/community/discussions/46757 that "@depdendabot merge command does not work" - we struggled with this for a while when testing a few months back before deciding to pause adopting this (merge queues are particularly useful for dependabot PRs where you likely have a stack of them that you want to approve and forget).

The article doesn't mention k3d (https://k3d.io/) which is a variant of k3s that runs in docker (rather than a VM) - very nice for k8s dev/test on developer workstations.

It integrates very nicely with https://tilt.dev/ also (another very useful tool for k8s related dev/test).

See https://en.wikipedia.org/wiki/List_of_Intel_manufacturing_si... - Intel has a 14nm in the EU (Ireland) and has planned a 7nm fab also - so "the EU" also plays in this space. A TSMC fab also would be good too of course but things aren't that bad.

Check out rqlite (https://github.com/rqlite/rqlite) for that functionality - "rqlite is a lightweight, distributed relational database, which uses SQLite as its storage engine. Forming a cluster is very straightforward, it gracefully handles leader elections, and tolerates failures of machines, including the leader. rqlite is available for Linux, macOS, and Microsoft Windows."

Nice summary. Did you test support for handling multiple changes to a single project in parallel? The only CI Platform I've found that tries to handle this in any meaningful way is OpenStack Zuul (https://zuul-ci.org/) and https://docs.openstack.org/infra/zuul/user/gating.html#testi... for details of the parallel support.

Do others have this need? Or are people generally focusing on keeping CI runs short and landing changes in a serial fashion?