terraform-aws-github-runner
action-debugger
| terraform-aws-github-runner | action-debugger | |
|---|---|---|
| 17 | 3 | |
| 0 | 21 | |
| - | - | |
| 9.6 | 2.1 | |
| 8 months ago | 3 months ago | |
| HCL | JavaScript | |
| MIT License | MIT License |
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.
terraform-aws-github-runner
- Show HN: Managed GitHub Actions Runners for AWS
- Show HN: Open-source x64 and Arm GitHub runners. Reduces GitHub Actions bill 10x
- Terraform module for scalable GitHub action runners on AWS
- Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
- Any tips on how to run auto scaling self-hosted GitLab runners well?
- Auto scaling Self-Hosted solution for GitHub Actions?
-
DeepFlow uses Spot Instances to speed up GitHub Action exploration
Terraform: Autoscale AWS EC2 as GitHub Runner with Terraform and AWS Lambda
action-debugger
-
The Pain That Is GitHub Actions
There definitely are a ton of issues with GitHub actions. To add to the OP's list:
- Self-hosting on your aws/gcp/azure account can get a little tricky. `actions-runner-controller` is nice but runs your workflows within a docker container in k8s, which leads to complex handling for isolation, cost controls because of NAT etc.
- Multi-arch container builds require emulation and can be extremely slow by default.
- The cache limits are absurd.
- The macos runners are slow and overpriced (arguably, most of their runners are).
Over the last year, we spent a good amount of time solving many of these issues with WarpBuild[1]. Having unlimited cache sizes, remote multi-arch docker builders with automatic caching, and ability to self-host runners in your aws/gcp/azure account are valuable to minimize cost and optimize performance.
[1] https://warpbuild.com
-
Terraform module for scalable GitHub action runners on AWS
We maintain a little action called Action-Debugger that let's you ssh into a running GitHub action workflow to help debug pesky issues. It has a few additional features when you use it with our runners but works very well by itself.
https://docs.warpbuild.com/tools/action-debugger
https://github.com/WarpBuilds/action-debugger
-
Show HN: WarpBuild – x86-64 and arm GitHub Action runners for 30% faster builds
[2] https://github.com/WarpBuilds/action-debugger, h/t to tmate
Making builds faster by providing optimal hardware and configurations across CI providers is the first step in our mission to make build engineering better.
I’d love your feedback on the product and thoughts on other CI pain points we could solve to enable better collaboration and developer experience.
What are some alternatives?
terraform-aws-oidc-github - Terraform module to configure GitHub Actions as an OpenID Connect (OIDC) identity provider in AWS.
action - RunsOn.com action to deploy ephemeral and cheap self-hosted runners for your workflows, in your AWS account
aws-toolkit-vscode - Amazon Q, CodeCatalyst, Local Lambda debug, SAM/CFN syntax, ECS Terminal, AWS resources
awesome-github-actions-runners - Save $$$ and make GitHub Actions go brrr with 3rd-party runners ⚡🤖
serverless-iam-roles-per-function - Serverless Plugin for easily defining IAM roles per function via the use of iamRoleStatements at the function level.
magic-nix-cache - Save 30-50%+ of CI time without any effort or cost. Use Magic Nix Cache, a totally free and zero-configuration binary cache for Nix on GitHub Actions.