blob
actions-runner-controller
blob | actions-runner-controller | |
---|---|---|
1 | 31 | |
- | 4,255 | |
- | 2.5% | |
- | 9.1 | |
- | 4 days ago | |
Go | ||
- | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
blob
-
Modern CI Is Too Complex and Misdirected
> Bazel has remote execution and remote caching as built-in features. Hey - those are built-in features of modern CI systems too! So here's a thought experiment: if I define a build system in Bazel and then define a server-side Git push hook so the remote server triggers Bazel to build, run tests, and post the results somewhere, is that a CI system? I think it is! A crude one. But I think that qualifies as a CI system.
Bazel can be a pain. Integration with external package managers is unnatural, hermetic toolchains are tricky, naively-written rules end up using system-provided utilities, breaking reproducibility.
But the remote execution API (besides feeling like magic) lets you treat your CI as "just another user" by design, unning the same `bazel test //...` or whatever else. This means
- the CI DSL/YAML files tend to have mostly publishing and other CI-specific information in then (this feels right)
- you get to debug your build pipeline locally
- you are actually testing the ability of a new user to pull the repo, build, and have everything just work. There is no special CI build environment that users implicit have to match.
- tangentially: the remote execution API is beautiful in its simplicity:
https://github.com/bazelbuild-remote-apis/blob/master/build/...
actions-runner-controller
-
Using Kaniko to Build and Publish container image with Github action on Github Self-hosted Runners
To set-up the self-hosted runner, an Action Runner Controller (ARC) and Runner scale sets application will be installed via helm. This post will be using Azure Kubernetes Service and ARC that is officialy maintained by Github. There is another ARC that is maintained by the community. You can follow the discussion where github adopted the ARC project into a full Github product here
-
Show HN: DimeRun v2 – Run GitHub Actions on AWS EC2
Before this we were using https://github.com/actions/actions-runner-controller but that's running on K8s instead of VMs. So along with common limitations of running CI jos in K8s/container, it cannot have exactly the same environment as the official GitHub runners. Maintaining a K8s cluster was also very difficult.
-
Terraform module for scalable GitHub action runners on AWS
ARC is great for running GitHub Actions on Kubernetes:
https://github.com/actions/actions-runner-controller
-
Best CI/CD for AWS services?
Almost all of our cicd, builds run on GitHub. I'm talking cypress tests, deployments via terraform and helm to over 25 environments, all backend tests, daily test runs etc. Overall we were racking up a cost of almost 20k on GitHub. With the ARC deployed and using spot instances I think our total infrastructure costs went up about 4-5k even though we added more actions. If we switched back to their runners we'd probably be around 25k at this point.
-
Running helm from within network
What else needs to be moved to my artifactory (charts - https://github.com/actions/actions-runner-controller/tree/master/charts ) - if so tar or entire folder or anything else ? ) What should the above steps correspond to?
-
Action-runner-controller & Enterprise Git
You need to use the steps in the repo instead of the steps on the docs if you're using enterprise server.
-
GitHub support for Actions Runner Controller (ARC) emerging in docs!
Honestly not a fan of Github docs.....I feel like the ones in the repo are much clearer and easier to understand/read.
-
How much work does it take to operate a self-hosted GitHub runners?
Its pretty easy to set up honestly. Deploy this on your k8s cluster https://github.com/actions/actions-runner-controller and a runnerDeployment and youre good to go.
-
Self-Hosted runner on Kubernetes
Trying to use the Actions Runner Controller (https://github.com/actions/actions-runner-controller) to utilize self-hosted runners. I keep getting this error on the controller.
-
AKS cluster w/ GitHub App and Actions Runner Controller
I'm convinced one of (or a combination) of things is happening here in regards to authentication. This GH enterprise account is configured with SAML. I feel like that is a valid data point. I'm using https://github.com/actions/actions-runner-controller as a reference guide for what I should be doing. I suspect whoever is Owner of this organization has modified what I can do as a user. The steps in the doc where I can actually Install the Application isn't available to me. When configuring the GitHub App I'm given two options. I select the option for "this account only" knowing the documentation says it is possible to use this Github App with a repo in the Organization as long as I have Admin privileges or I'm the owner.
What are some alternatives?
runner - The Runner for GitHub Actions :rocket:
helm-charts - Jenkins helm charts
mkdkr - mkdkr = Makefile + Docker
turnstyle - 🎟️A GitHub Action for serializing workflow runs
cache - Cache dependencies and build outputs in GitHub Actions
azure-pipelines-agent - Azure Pipelines Agent 🚀
ghat - 🛕 Reuse GitHub Actions workflows across repositories
actions-runner-
github-action-tester - Run tests when pull-requests are opened, or commits pushed.
jenkins-std-lib - Bringing the Zen of Python to Jenkins.
terraform-aws-github-runner - Terraform module for scalable GitHub action runners on AWS