-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci-builder: fix build #9042
ci-builder: fix build #9042
Conversation
Was broken with #8920 due to the new `jq` dependency not being present in the builder image. Fix by installing `jq` in the builder image.
WalkthroughWalkthroughThe Dockerfile has been updated to change a package installation and to use a newer base image. The Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
The foundry install script uses `jq` so we must install `jq` as early as possible in `ci-builder` to ensure that its always present. Follow up to #9042 which fixes the broken build from #8920. I don't think that #8920 broke the fix in this commit so perhaps the build was broken longer than we thought? Either way, we need new forge version in CI that was introduced in #9038 so we need a successful build of `ci-builder`.
The foundry install script uses `jq` so we must install `jq` as early as possible in `ci-builder` to ensure that its always present. Follow up to #9042 which fixes the broken build from #8920. I don't think that #8920 broke the fix in this commit so perhaps the build was broken longer than we thought? Either way, we need new forge version in CI that was introduced in #9038 so we need a successful build of `ci-builder`.
Was broken with ethereum-optimism#8920 due to the new `jq` dependency not being present in the builder image. Fix by installing `jq` in the builder image.
The foundry install script uses `jq` so we must install `jq` as early as possible in `ci-builder` to ensure that its always present. Follow up to ethereum-optimism#9042 which fixes the broken build from ethereum-optimism#8920. I don't think that ethereum-optimism#8920 broke the fix in this commit so perhaps the build was broken longer than we thought? Either way, we need new forge version in CI that was introduced in ethereum-optimism#9038 so we need a successful build of `ci-builder`.
Description
Was broken with #8920
due to the new
jq
dependency not being present in the builder image.Fix by installing
jq
in the builder image.