techno-tim / k3s-ansible

The easiest way to bootstrap a self-hosted High Availability Kubernetes cluster. A fully automated HA k3s etcd install with kube-vip, MetalLB, and more. Build. Destroy. Repeat.
https://technotim.live/posts/k3s-etcd-ansible/
Apache License 2.0
2.41k stars 1.05k forks source link

Add Concurrency GHA Feature to CI #386

Closed timothystewart6 closed 9 months ago

timothystewart6 commented 1 year ago

CI fails a lot, most of it is because the nature of our machines but some of it might be due to concurrency.

We might want to limit concurrency using this https://docs.github.com/en/actions/using-jobs/using-concurrency

We might also want to consider running the individual jobs serially, rather than in parallel.

The upside is that this might help with build failures The downside is that builds will take loner (but when they fail we have to manually intervene which takes the longest)

timothystewart6 commented 9 months ago

this was fixed by https://github.com/techno-tim/k3s-ansible/pull/389.

we don't need concurrency now