Updating Docker publishing with Github Actions

[ShahanaFarooqui]

Summary by CodeRabbit

• New Features

  • Added a new GitHub Actions workflow to build and release Docker images based on tags and manual triggers.
  • Introduced multi-stage builds in Dockerfile for different architectures (arm32v7, arm64v8, amd64).

• Updates

  • Updated CircleCI configuration for multi-platform Docker builds with QEMU and Buildx setup.
  • Renamed and restructured CircleCI jobs for better clarity and efficiency.

[coderabbitai]

Warning

Review failed

The pull request is closed.

Walkthrough

The updates focus on optimizing and modernizing Docker and CI/CD pipelines. CircleCI configuration is revamped with Docker Buildx and QEMU for multi-platform builds, while a new GitHub workflow, docker-release.yml, automates Docker image releases. The Dockerfile now supports multi-stage builds tailored to different architectures, improving efficiency and scalability.

Changes

File	Change Summary
.circleci/config.yml	Updated configuration version to 2.1, restructured job names and steps, introduced Docker Buildx for multi-platform builds, and added a new Python 3.8 executor.
.github/workflows/docker-release.yml	Added a new workflow for building and pushing Docker images based on tags and manual triggers, with jobs utilizing QEMU, Buildx, and various GitHub Actions for streamlined release automation.
Dockerfile	Introduced multi-stage builds for different architectures (arm32v7, arm64v8, amd64), configured dependencies and build processes for each, and optimized the base image to node:18-alpine.

Sequence Diagram(s)

sequenceDiagram
    participant Developer
    participant GitHub
    participant CircleCI
    participant DockerHub

    Developer->>GitHub: Push code/trigger workflow
    GitHub->>CircleCI: Trigger CircleCI jobs
    CircleCI->>CircleCI: Setup QEMU and Docker Buildx
    CircleCI->>DockerHub: Build and push multi-platform image
    Developer->>GitHub: Trigger docker-release workflow
    GitHub->>DockerHub: Build and push release images

Loading

Poem

A rabbit hops through Docker fields,
With Buildx magic, power yields.
Multi-arch dreams now take flight,
From CI lands to release night.
Circle spins, workflows align,
In code’s embrace, the stars now shine. 🌟

---

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

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.