Add Docker build and push called workflow

[brettcurtis]

Summary by CodeRabbit

• Chores
  • Introduced a GitHub Actions workflow for building and pushing Docker images to Google Artifact Registry.

[coderabbitai]

Walkthrough

The new build-and-push.yml file introduces a GitHub Actions workflow designed to build and push Docker images to Google Artifact Registry. Triggered by a workflow call, it automates steps like code checkout, Google credential management, Docker Buildx setup, Artifact Registry login, and Docker image building and pushing.

Changes

Files	Change Summary
.github/workflows/build-and-push.yml	New GitHub Actions workflow to automate building and pushing Docker images to Google Artifact Registry.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow Call
    participant GitHub Actions
    participant Google Artifact Registry
    
    Workflow Call->>GitHub Actions: Trigger "Build and Push Called Workflow"
    GitHub Actions->>GitHub Actions: Checkout Code
    GitHub Actions->>GitHub Actions: Create Google Credentials
    GitHub Actions->>GitHub Actions: Setup Docker Buildx
    GitHub Actions->>Google Artifact Registry: Login to Artifact Registry
    GitHub Actions->>GitHub Actions: Build Docker Image
    GitHub Actions->>Google Artifact Registry: Push Docker Image

Loading

---

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1da9ccd and fbceaa5.

Files selected for processing (1)

• .github/workflows/build-and-push.yml (1 hunks)

Additional comments not posted (7)

.github/workflows/build-and-push.yml (7)

1-4: Workflow metadata configuration is correct.

The workflow name and trigger event are properly defined.

---

5-40: Workflow inputs configuration is comprehensive and correct.

The inputs cover essential parameters with appropriate default values and types.

---

47-51: Checkout step is correctly configured.

The step uses the latest version of the actions/checkout action.

---

56-63: Create credentials step is correctly configured.

The step uses the google-github-actions/auth action with appropriate inputs to generate an access token.

---

68-69: Docker Buildx setup step is correctly configured.

The step uses the latest version of the docker/setup-buildx-action action.

---

74-79: Docker login step is correctly configured.

The step uses the docker/#-action action with the generated access token for authentication.

---

85-94: Build and push step is correctly configured.

The step uses the docker/build-push-action action with appropriate inputs for tags, cache settings, context, Dockerfile, build arguments, and push flag.