earthly
act
Our great sponsors
earthly | act | |
---|---|---|
18 | 145 | |
10,789 | 49,985 | |
4.2% | 3.2% | |
9.8 | 9.2 | |
7 days ago | about 22 hours ago | |
Go | Go | |
Mozilla Public License 2.0 | 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.
earthly
-
Cache is King: A guide for Docker layer caching in GitHub Actions
Also CACHE keyword, for cache mounts. Makes incremental tools like compilers work well in the context of dockerfiles and layer caches.
That can extend beyond just producing docker iamges as well. Under the covers the CACHE keyword is how lib/rust in Earthly makes building Rust artifacts in CI faster.
-
Is your makefile supposed to be a justfile?
earthly
-
Show HN: Earthly 0.7.0
A few of us will be around to answer questions if anyone has any. I myself worked only worked on the chmod feature which was pretty trivial.
- Earthly CI: Launching a new era for CI
-
Containerize CI pipelines with Earthly
# cat Makefile BIN_PATH = $(shell pwd)/bin $(shell mkdir $(BIN_PATH) &>/dev/null) EARTHLY = $(BIN_PATH)/earthly earthly: ifeq (,$(wildcard $(EARTHLY))) curl -L https://github.com/earthly/earthly/releases/download/v0.6.23/earthly-linux-amd64 -o $(EARTHLY) chmod +x $(EARTHLY) endif
- Earthly - The effortless ci/cd framework that runs anywhere
-
GitHub Actions Is Down
I started to bring awareness to the Earthfiles goofy license, but it seems they've switched to MPL! https://github.com/earthly/earthly/releases/tag/v0.6.15
The (unfortunately named) Dagger is also an entry into that space: https://github.com/dagger/dagger#readme (Apache 2)
-
Please name some open source projects which are collecting small user analytics metrics and how
- https://github.com/earthly/earthly/tree/main/analytics
-
Dagger: a new way to build CI/CD pipelines
Another *monster* difference is that Dagger is (at least currently) Apache 2: https://github.com/dagger/dagger/blob/v0.2.4/LICENSE but Earthly went with BSL: https://github.com/earthly/earthly/blob/v0.6.12/LICENSE
That means I'm more likely to submit bugs and patches to Dagger, and I won't touch Earthly
-
Migrating Your Open Source Builds Off Of Travis CI
Example build steps for a go application
act
-
How to debug GitHub actions. Real-world example
When it comes to the alternatives to tmate, there is another great debugging tool that you could check out. It is called act and it allows you to run GitHub Actions code on your local machine making debugging even easier. It has its own limitations and some learning curve but overall it is another tool you should use if you can’t fix the CI bugs by connecting directly into the running action with the tmate.
- Using my new Raspberry Pi to run an existing GitHub Action
-
Show HN: Open-source x64 and Arm GitHub runners. Reduces GitHub Actions bill 10x
Could you upload your build of GitHub's runner image to Docker Hub?
This would be quite useful for users of other GitHub Actions clones like act [0].
-
Git commit messages are useless
> These kinds of commit messages are typically an indicator of a broken process where somebody needs to commit to see something happen, like a deployment or build process, and aren't able to assert that stuff works locally.
This is one of my biggest pet peeves with services like github actions. Something running locally like "act" [1] isn't sufficient because it doesn't have everything github has and is extra friction anyway to get everyone to use it for testing.
-
Essential Command Line Tools for Developers
View on GitHub
-
What’s with DevOps engineers using `make` of all things?
If you use Github actions, act is incredibly useful. It can be used to test your GH actions, but also serves as an interface for running tasks locally.
-
Streamlining CI/CD Pipelines with Code: A Developer's Guide
That's something that often is difficult or basically impossible. Except for maybe GitHub actions through Act (https://github.com/nektos/act). I'd still lean to something in the yaml sphere if it eventually would be used in deployment pipelines and such. For example a solution incorporating ansible.
It also seems to me that the argument you make is mostly focused on the building step? Earthly certainly seems focused on that aspect.
-
GitHub Actions Are a Problem
I feel I'm being trolled, but I'll bite and accept the resulting downvotes
I don't think treating every mention of act as an opportunity for airing of personal grievances is helpful in a discussion when there's already ample reports of people's concrete issues with it, had one looked at the 800 issues in its repo https://github.com/nektos/act/issues?q=is%3Aissue or the 239 from gitea's for https://gitea.com/gitea/act_runner/issues or whatever is going on with Forgejo's fork https://code.forgejo.org/forgejo/act .
But, as for me specifically, there are two and a half answers: I wanted to run VSCodium's build locally, which act for sure puked about. Then, while trying to troubleshoot that, I thought I'd try something simpler and have it run the lint job from act's own repo <https://github.com/nektos/act/blob/1252e551b8672b1e16dc8835d...> to rule out "you're holding it wrong" type junk. It died with
[checks/lint] Failure - Main actions/setup-go@v3
-
How Steve Jobs Saved Apple with the Online Apple Store
https://twitter.com/mitsuhiko/status/1720410479141487099 :
> GitHub Actions currently charges $0.16 per minute* for the macOS M1 Runners. That comes out to $84,096 for 1 machine year*
GitHub Runner is written in Go; it fetches tasks from GitHub Actions and posts the results back to the Pull Request that spawned the build.
nektos/act is how Gitea Actions builds GitHub Actions workflow YAML build definition documents. https://github.com/nektos/act
https://twitter.com/MatthewCroughan/status/17200423527675700... :
> This is the macOS Ventura installer running in 30 VMs, in 30 #nix derivations at once. It gets the installer from Apple, automates the installation using Tesseract OCR and TCL Expect scripts. This is to test the repeatability. A single function call `makeDarwinImage`.
With a Multi-Stage Dockerfile/Containerfild, you can have a dev environment like xcode or gcc+make in the first stage that builds the package, and then the second stage the package is installed and tested, and then the package is signed and published to a package repo / app store / OCI container image repository.
SLSA now specifies builders for signing things correctly in CI builds with keys in RAM on the build workers.
"Build your own SLSA 3+ provenance builder on GitHub Actions" https://slsa.dev/blog/2023/08/bring-your-own-builder-github
- Overview
What are some alternatives?
dagger - Application Delivery as Code that Runs Anywhere
reverse-rdp-windows-github-actions - Reverse Remote Desktop into Windows on GitHub Actions for Debugging and/or Job Introspection [GET https://api.github.com/repos/nelsonjchen/reverse-rdp-windows-github-actions: 403 - Repository access blocked]
Dagger.jl - A framework for out-of-core and parallel execution
cache - Cache dependencies and build outputs in GitHub Actions
dagger-for-github - GitHub Action for Dagger
docker-flask-example - A production ready example Flask app that's using Docker and Docker Compose.
action-tmate - Debug your GitHub Actions via SSH by using tmate to get access to the runner system itself.
pipeline - A cloud-native Pipeline resource.
LSPatch - LSPatch: A non-root Xposed framework extending from LSPosed
Phoenix - Peace of mind from prototype to production
virtual-environments - GitHub Actions runner images [Moved to: https://github.com/actions/runner-images]