feat(ci): add dev image build and cache support

[corporal9736]

No description provided.

[coderabbitai]

Walkthrough

This update introduces enhancements and a new workflow to the project's GitHub Actions, focusing on Docker image handling. It optimizes Docker image caching in the production build workflow and establishes an automated process for building and testing Docker images for development purposes. The changes streamline CI/CD pipelines, improve build times, and ensure that Docker images are reliably built and tested.

Changes

Files	Change Summaries
.github/workflows/build-docker-prod.yml	Added cache optimization for Docker builds.
.github/workflows/build-test-docker-dev.yml	New workflow for building and testing dev Docker image, including setup and push based on conditions.

🐇✨
In the realm of code and nightly builds,
Where Docker images dance and twirl,
A rabbit hopped, with skills so deft,
Spinning up containers, left and right unfurled.
"To cache! To build!" it cheerfully calls,
Through pipelines vast, its magic sprawls.
🚀💾

---

Recent Review Details

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 277dfa7 and 2ea0ff5.

Files selected for processing (2)

• .github/workflows/build-docker-prod.yml (1 hunks)
• .github/workflows/build-test-docker-dev.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/build-docker-prod.yml

Additional comments not posted (3)

.github/workflows/build-test-docker-dev.yml (3)

3-11: Consider adding more trigger conditions for enhanced flexibility.

While the workflow is currently triggered on pushes and pull requests to the dev branch, and manually via workflow_dispatch, you might want to consider adding more trigger conditions. For instance, including tags or specific paths could provide more control over when the workflow runs, especially for changes that directly affect the Docker build process.

---

12-14: Validate the choice of registry and image name.

Ensure that the REGISTRY and IMAGE_NAME environment variables are correctly set for your project's needs. The current settings use GitHub Container Registry (ghcr.io) and a specific image name (SageSeekerSociety/cheese-frontend-dev). Confirm that these values align with your project's Docker registry and naming conventions.

---

20-22: Review permissions settings for security.

The workflow grants read permissions to contents and write permissions to packages. While these settings are likely appropriate for the tasks at hand, it's good practice to periodically review and minimize permissions to adhere to the principle of least privilege, enhancing the security posture of your CI/CD pipeline.

---

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 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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.
• 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.

[coderabbitai]

Actionable comments posted: 1

[coderabbitai]

Optimize Docker build and push step with caching.

The Docker build and push step is configured to use GitHub Actions' caching (cache-from: type=gha and cache-to: type=gha,mode=max). This is a great practice for speeding up builds. However, consider specifying more granular cache keys based on your project's structure and dependencies to further optimize caching efficiency. For example, using a combination of the base image version, Dockerfile changes, and dependency manifest files as part of the cache key can help ensure that the cache is invalidated appropriately when necessary.