chore: Independent CI #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kmannislands
commented
Jun 19, 2025
janishorsts
reviewed
Jun 19, 2025
Collaborator
|
I was not aware that GCP has a public mirror of the Docker registry and is free for anonymous users. Using ECR public mirroring causes too much friction (requires renaming image names by prefixing with "docker/"). This is how I set up mirroring in my PR |
gilescope
approved these changes
Jun 22, 2025
kmannislands
force-pushed
the
get-ci-working
branch
2 times, most recently
from
edf12f7 to
987e863
Compare
kmannislands
force-pushed
the
get-ci-working
branch
from
9d88886 to
860e13d
Compare
…ns setup. TODO: switch to ECR public or google public mirror instead or just removing mirroring entirely?
…r than doc lint) that have run so far
…t-ci-working as the buildkitd image--unclear why. perhaps a sequencing logic issue where the CI builds attempt to use the previous binary and cannot handle a failure of the previous job? restore cache from to see if that is somehow related
… settings in the UI need adjustment
…e registry paths with dind repo terms
…g a single repository for now
kmannislands
force-pushed
the
get-ci-working
branch
from
860e13d to
e4380a1
Compare
…t intermediary img
Author
* chore(earthbuild): fix +lint-all * chore: run Podman CI Ubuntu on any pull_request * remove unused verbose field * undo Podman CI Ubuntu workflow changes
Currently, the race-test image for a CI build step is generated the step before with the new EarthBuild name: ghcr.io/earthbuild/earthbuild:buildkitd-race-test. The next step references the original Earthly name: earthly/buildkitd:race-test. This causes a build failure. Update to the new name. Co-authored-by: Squirrel <[email protected]>
* feat: don't login to docker if not using docker
* feat: don't login to docker if not using docker * fix: examples1/grpc example
danielschlegel
added a commit
that referenced
this pull request
Aug 13, 2025
This appears to be a **major rebranding effort** from "Earthly" to "Earthbuild". Here are the key changes: - All references to "earthly" have been systematically changed to "earthbuild" - Binary name changed from `earthly` to `earthbuild` - Repository references updated from `earthly/earthly` to `earthbuild/earthbuild` - Organization references changed from "earthly-technologies" to "earthbuild-technologies" - Domain references changed from `earthly.dev` to `earthbuild.dev` - Updated all BuildKite, CircleCI, and GitHub Actions configurations - Changed environment variables from `EARTHLY_*` to `EARTHBUILD_*` - Updated download URLs to point to new repository locations - Modified Docker registry mirrors and authentication - Extensive updates to README files across the project - Updated installation instructions and examples - Changed documentation references throughout - Updated changelog to reflect the rebranding - Deleted various configuration files (like `.earthly_version_flag_overrides`, `.earthlyignore`) - Removed cloud-related documentation and features - Cleaned up various CI configuration files - **Latest commit (44d53a6)**: "docs: Summary of Changes Made" - **Previous work included**: - Independent CI setup (#1) - Fork testing for examples (#38) - Removal of satellite CI references (#24) - Complete removal of Cloud features (earthly#4325) - README clarification about fork status (#4) - Updated container names from `earthly-*` to `earthbuild-*` - Changed secret organization references - Updated example repository references - Modified installation scripts and bootstrap processes This represents a **complete fork and rebranding** of the Earthly project to create "Earthbuild" as an independent project. The changes are comprehensive, touching every aspect of the codebase from build scripts to documentation to maintain consistency with the new brand identity.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial exploratory work to discover blockers for CI on main
earthbuild(formerlyearthly) repository.This is ahead of updates to some of the dependency repositories:
buildkitd: kick ci tyres buildkit#1dind: chore: fix CI workflow dind#1This is a "stage 0" bootstrap where we'll still be using the existing "earthly" binaries to build "earthbuild" with the eventual goal of "stage 1," building
earthbuildwithearthbuildNotes for follow up:
.mdfiles but there was no pre-commit (at least as far as I noticed) to enforce this at commit time. This is slightly annoying and we should consider introducing a tool like pre-commitPROJECTsyntax seemed to throw my LLM tool for a loop (it was hard to convince it this is not relevant to the org used bySAVE IMAGE). It raises the point thatPROJECTdoesn't make sense in a post-satellite world. We should consider deprecating this command in aVERSION 0.9of the syntax (it should be ignored in the immediate fork)