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: install rocksdb dependencies in CI #568

Merged
merged 2 commits into from
Oct 8, 2024
Merged

ci: install rocksdb dependencies in CI #568

merged 2 commits into from
Oct 8, 2024

Conversation

holtgrewe
Copy link
Contributor

@holtgrewe holtgrewe commented Oct 8, 2024

Summary by CodeRabbit

  • Chores
    • Updated GitHub Actions workflows to include new steps for installing necessary dependencies.
    • Enhanced the Linting job by ensuring required system packages are installed prior to linting checks.

Copy link
Contributor

coderabbitai bot commented Oct 8, 2024

Walkthrough

The pull request introduces modifications to two GitHub Actions workflow files: .github/workflows/release-please.yml and .github/workflows/rust.yml. Both files now include a new step for installing the system dependency librocksdb-dev. In the release-please.yml file, this step is conditional on the creation of a release, while in the rust.yml file, it precedes the installation of the stable toolchain in the Linting job. Additionally, minor indentation corrections were made in the rust.yml file.

Changes

File Path Change Summary
.github/workflows/release-please.yml Added "Install dependencies" step in cargo-release job to install librocksdb-dev, conditional on release_created.
.github/workflows/rust.yml Added "Install dependencies" step in the Linting job to install librocksdb-dev; corrected indentation for the "Checkout repository" step.

Possibly related PRs

🐇 In the workflows where bunnies play,
Dependencies hop in a joyful way.
With rocks and sqlite, all set to go,
Linting and releasing, watch the code flow!
A little tweak here, a step added there,
Now our builds are light as air! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 477e8e1 and 7361211.

📒 Files selected for processing (2)
  • .github/workflows/release-please.yml (1 hunks)
  • .github/workflows/rust.yml (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • .github/workflows/release-please.yml
  • .github/workflows/rust.yml

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>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@holtgrewe holtgrewe enabled auto-merge (squash) October 8, 2024 10:58
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Outside diff range and nitpick comments (2)
.github/workflows/rust.yml (1)

37-39: Consider adding dependency installation to other jobs

The new dependency installation step is currently only added to the Linting job. However, these dependencies (especially RocksDB) might be required for other jobs as well, particularly the Testing job.

To ensure consistency across the CI environment and prevent potential issues:

  1. Consider adding the dependency installation step to the Testing job.
  2. If the Formatting job doesn't require these dependencies, you can leave it as is.

This approach will help maintain a consistent environment across different CI stages and reduce the risk of environment-related failures.

.github/workflows/release-please.yml (1)

40-42: Enhance dependency installation step

The addition of this step aligns well with the PR objective of installing RocksDB dependencies in CI. However, consider the following improvements:

  1. Make this step conditional on release creation, similar to other steps in this job:

    - name: Install dependencies
      if: ${{ needs.release-please.outputs.release_created }}
      run: sudo apt-get update && sudo apt-get install -y librocksdb-dev libsqlite3-dev
  2. Consider pinning package versions to ensure build consistency:

    run: sudo apt-get update && sudo apt-get install -y librocksdb-dev=<version> libsqlite3-dev=<version>
  3. If running in a container or with root privileges, you can omit sudo. Otherwise, add sudo to ensure the command has the necessary permissions.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 7fefaec and 477e8e1.

📒 Files selected for processing (2)
  • .github/workflows/release-please.yml (1 hunks)
  • .github/workflows/rust.yml (1 hunks)
🧰 Additional context used
🔇 Additional comments (2)
.github/workflows/rust.yml (1)

Line range hint 1-39: Overall approval of changes

The addition of the dependency installation step is a positive improvement to the CI workflow. It addresses the PR objective of installing RocksDB dependencies in CI.

The changes are well-placed and contribute to a more robust CI process. With the suggested improvements implemented, this change will enhance the reliability and consistency of the build environment.

🧰 Tools
🪛 actionlint

41-41: the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

.github/workflows/release-please.yml (1)

Line range hint 1-101: Overall workflow improvement

The addition of the dependency installation step enhances the CI process by ensuring that necessary libraries (RocksDB and SQLite) are available for the build. This change aligns well with the PR objective of installing RocksDB dependencies in CI.

The placement of the new step before the toolchain installation is appropriate. However, consider implementing the suggestions in the previous comment to further improve the workflow's efficiency and consistency.

🧰 Tools
🪛 actionlint

44-44: the runner of "actions-rs/toolchain@v1" action is too old to run on GitHub Actions. update the action's version to fix this issue

(action)

Comment on lines 37 to 38
- name: Install dependencies
run: apt-get update && apt-get install -y librocksdb-dev libsqlite3-dev
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Enhance dependency installation step

The new step for installing dependencies is a good addition. However, consider the following improvements:

  1. Use sudo to ensure the command has the necessary permissions.
  2. Add the -y flag to apt-get update to automatically answer yes to prompts.
  3. Use --no-install-recommends to minimize installed packages.
  4. Add error handling and verbosity for better debugging.

Here's an improved version of the step:

      - name: Install dependencies
        run: |
          sudo apt-get update -y
          sudo apt-get install -y --no-install-recommends librocksdb-dev libsqlite3-dev
        shell: bash

This change ensures proper permissions, reduces unnecessary package installations, and provides a more robust command execution.

@holtgrewe holtgrewe disabled auto-merge October 8, 2024 11:04
Copy link

codecov bot commented Oct 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.01%. Comparing base (bf54266) to head (7361211).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #568      +/-   ##
==========================================
+ Coverage   73.99%   74.01%   +0.02%     
==========================================
  Files          26       26              
  Lines        9849     9857       +8     
==========================================
+ Hits         7288     7296       +8     
  Misses       2561     2561              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@holtgrewe holtgrewe merged commit c1dfe6f into main Oct 8, 2024
11 checks passed
@holtgrewe holtgrewe deleted the ci-fix-rocksdb branch October 8, 2024 11:17
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.

1 participant