Skip to content
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

Merged
merged 1 commit into from
Jan 17, 2024
Merged

ci-builder: fix build #9042

merged 1 commit into from
Jan 17, 2024

Conversation

tynes
Copy link
Contributor

@tynes tynes commented Jan 17, 2024

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.

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.
@tynes tynes requested a review from a team as a code owner January 17, 2024 18:01
@tynes tynes requested a review from Inphi January 17, 2024 18:01
Copy link
Contributor

coderabbitai bot commented Jan 17, 2024

Walkthrough

Walkthrough

The Dockerfile has been updated to change a package installation and to use a newer base image. The jq package installation was altered during the go-build phase, and the base image has been switched to debian:bullseye-slim, indicating an update to the build environment and possibly the dependencies for the Go application.

Changes

File Path Change Summary
ops/docker/ci-builder/Dockerfile Replaced jq package installation in go-build stage; updated base image to debian:bullseye-slim.

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?

Share

Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit-tests for this file.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@refcell refcell enabled auto-merge January 17, 2024 18:05
@refcell refcell added this pull request to the merge queue Jan 17, 2024
Merged via the queue into develop with commit 247225b Jan 17, 2024
66 checks passed
@refcell refcell deleted the fix/ci-builder branch January 17, 2024 18:32
tynes added a commit that referenced this pull request Jan 17, 2024
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`.
github-merge-queue bot pushed a commit that referenced this pull request Jan 17, 2024
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`.
dshiell pushed a commit to polymerdao/optimism-dev that referenced this pull request Jan 22, 2024
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.
dshiell pushed a commit to polymerdao/optimism-dev that referenced this pull request Jan 22, 2024
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`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants