ci: migrate docker builds to GitHub Actions (except op-deployer)#18821
Merged
falcorocks merged 2 commits intodevelopfrom Jan 28, 2026
Merged
ci: migrate docker builds to GitHub Actions (except op-deployer)#18821falcorocks merged 2 commits intodevelopfrom
falcorocks merged 2 commits intodevelopfrom
Conversation
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
falcorocks
force-pushed
the
falco/cci-to-gha-migration-clean
branch
8 times, most recently
from
842f85f to
3d6df5d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #18821 +/- ##
==========================================
+ Coverage 75.4% 76.0% +0.6%
==========================================
Files 188 188
Lines 11715 10948 -767
==========================================
- Hits 8839 8331 -508
+ Misses 2730 2473 -257
+ Partials 146 144 -2
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
falcorocks
force-pushed
the
falco/cci-to-gha-migration-clean
branch
4 times, most recently
from
356129b to
533f338
Compare
falcorocks
changed the title
Migrate Docker image builds from CircleCI to GitHub Actions for all images except `op-deployer`. ## Changes **GitHub Actions:** - Build all images (except op-deployer) in GHA with multi-arch support (amd64/arm64) - Add scheduled daily builds at 2 AM UTC - Add cross-platform verification job - Push to `images` registry instead of `oss` - Rename jobs: `local` → `build`, `fork` → `build-fork` **CircleCI:** - Keep `op-deployer` builds in CircleCI (main, release, scheduled workflows) - Remove all other images from docker-build matrices ## Why op-deployer stays in CircleCI `op-deployer` embeds compiled Solidity contract artifacts via `go:embed`. The CircleCI pipeline has an existing `contracts-bedrock-build` job that compiles these artifacts and passes them via workspace attachment. Replicating this in GHA requires changes to the Dockerfile build process that need more work.
falcorocks
force-pushed
the
falco/cci-to-gha-migration-clean
branch
from
533f338 to
86e6afa
Compare
janjakubnanista
approved these changes
Jan 26, 2026
serpixel
approved these changes
Jan 28, 2026
Add merge_group event to triggers and build job condition so the workflow runs properly when PRs go through the merge queue.
6 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Migrate Docker image builds from CircleCI to GitHub Actions for all images except
op-deployer.Changes
GitHub Actions:
imagesregistry instead ofosslocal→build,fork→build-forkCircleCI:
op-deployerbuilds in CircleCI (main, release, scheduled workflows)Why op-deployer stays in CircleCI
op-deployerembeds compiled Solidity contract artifacts viago:embed. The CircleCI pipeline has an existingcontracts-bedrock-buildjob that compiles these artifacts and passes them via workspace attachment. Replicating this in GHA requires changes to the Dockerfile build process that need more work.