Added test with docker (CI)

[adimiko]

Summary by CodeRabbit

• Chores
  • Updated the workflow environment to improve build efficiency and compatibility.

[coderabbitai]

Warning

Rate Limit Exceeded

@adimiko has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 43 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 09612e2 and e9ff62d.

Walkthrough

The update involves transitioning the workflow's operating system from Windows to Ubuntu. This shift necessitates the use of Bash instead of PowerShell for script execution, accompanied by modifications to paths to conform to Unix-style formatting. This change aims to streamline operations within a Linux environment, potentially improving performance and compatibility.

Changes

File	Summary
.github/workflows/...	OS changed from windows-latest to ubuntu-latest, shell to bash, and Unix-style paths.

🐇✨
In a world of code and byte,
We hopped from Windows with delight.
To Ubuntu's lands, we take our script,
With Bash in hand, our code we've flipped.
Paths now twist in Unix style,
Our workflow runs, with a smile.
🚀🌌

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

• X
• Mastodon
• Reddit
• LinkedIn

---

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.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 5f177f8 and 09612e2.

Files selected for processing (1)

• .github/workflows/build.yaml (2 hunks)

Additional comments: 7

.github/workflows/build.yaml (7)

• 13-13: Ensure that all dependencies and tools used in the workflow are compatible with Ubuntu, given the switch from Windows.
• 29-29: The path ~/sonar/cache is correctly updated to Unix-style. Verify that this path aligns with the expected directory structure for caching on Ubuntu.
• 37-37: The path ./.sonar/scanner is correctly updated to Unix-style. Ensure that this directory is correctly referenced in all relevant steps of the workflow.
• 43-43: Switching the shell to bash is appropriate for Ubuntu. Ensure that all bash commands and scripts used in this step are compatible with bash syntax and semantics.
• 45-46: The commands to create the directory and update the dotnet SonarScanner tool are correctly formatted for bash. Ensure that the .sonar/scanner directory is the correct location for the tool installation.
• 52-52: Switching the shell to bash for the build and analyze step is consistent with the earlier shell change. Verify that the bash commands used here are compatible with bash syntax.
• 54-57: The commands to begin SonarScanner analysis, restore, build, and end the analysis are correctly formatted for bash. Ensure that the SonarCloud scanner tool is correctly configured and that the specified project key and organization match the project's settings on SonarCloud.