fix(ci,worker): update context of copier dockerfile to root

[nourbalaha]

Overview

This PR updated the context of copier.Dockerfile to the root folder

Summary by CodeRabbit

• Build Configuration
  • Updated GitHub Actions workflow to adjust Docker image build context.
  • Modified Dockerfile for worker copier to improve build process and dependency management.
  • Refined Docker image build and execution steps for enhanced clarity and specificity.

[coderabbitai]

Walkthrough

The pull request introduces modifications to the GitHub Actions workflow configuration and the Docker build process for the worker's copier service. The changes primarily focus on adjusting the build context in the workflow file and refining the Dockerfile for more precise file copying and dependency management. These updates enhance the clarity and specificity of the build process while changing the execution method of the application within the container.

Changes

File	Change Summary
.github/workflows/build_worker.yml	Modified Docker build context from ./worker to . for the docker_copier job
worker/copier.Dockerfile	- Replaced single COPY . . with multiple specific COPY commands - Added RUN go mod download step - Updated build command with explicit path - Modified final stage copy and execution instructions

Poem

🐰 A Rabbit's Build Ballet 🐰
Contexts shift, workflows align,
Dockerfiles dance, dependencies entwine,
From root to worker, paths now clear,
Copier's journey, no longer austere,
Build and deploy with rabbit-like might! 🚀

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 59301f4 and eed62a3.

📒 Files selected for processing (1)

• worker/copier.Dockerfile (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: ci-worker / test

🔇 Additional comments (4)

worker/copier.Dockerfile (4)

5-14: Well-structured file copying strategy!

The file copying strategy is excellent because it:

• Optimizes Docker layer caching by copying dependency files first
• Explicitly specifies file paths rather than using wildcards
• Maintains a clear separation between dependency files and source code

---

16-16: Excellent build configuration!

The build command follows container best practices:

• Disables CGO for static linking
• Uses -trimpath for reproducible builds

---

18-24: Proper runtime stage configuration!

The runtime stage is well configured:

• Uses minimal scratch image
• Maintains consistent paths with working directory
• Allows command override with CMD

---

5-14: Verify Docker build with root context.

The file paths are now correctly structured for root context. Please verify the Docker build works as expected:

✅ Verification successful

Docker paths verified successfully

All files and directories referenced in the Dockerfile exist at the correct paths relative to the repository root. The changes are properly structured for building with root context.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify Docker build from repository root
# Expected: All paths should be valid when building from root context

# Check if all referenced files exist
echo "Verifying file paths..."
files=(
    "go.work"
    "go.work.sum"
    "server/go.mod"
    "server/go.sum"
    "server/main.go"
    "worker/go.mod"
    "worker/go.sum"
    "worker/main.go"
    "server/pkg"
    "worker/cmd"
    "worker/internal"
    "worker/pkg"
)

for file in "${files[@]}"; do
    if [ ! -e "$file" ]; then
        echo "Error: $file not found"
        exit 1
    fi
done

Length of output: 940

---

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>, 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[netlify]

✅ Deploy Preview for reearth-cms canceled.

Name	Link
🔨 Latest commit	eed62a3
🔍 Latest deploy log	https://app.netlify.com/sites/reearth-cms/deploys/67878007d4881d0008f9e7dd

[coderabbitai]

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61a5e68 and 59301f4.

📒 Files selected for processing (2)

• .github/workflows/build_worker.yml (1 hunks)
• worker/copier.Dockerfile (1 hunks)

🔇 Additional comments (4)

worker/copier.Dockerfile (3)

5-7: Well-structured module setup!

Good job on organizing the COPY commands. This approach:

• Optimizes layer caching by copying module files first
• Correctly handles dependencies with the root context
• Maintains a clear separation between modules

---

9-9: LGTM: Proper dependency management.

Correct placement of go mod download after copying module files ensures efficient caching of dependencies.

---

11-16: Excellent build configuration!

The build stage is well-structured with:

• Organized source code copying by package
• Proper build flags for container deployment (-trimpath, CGO_ENABLED=0)
• Correct build target path for root context

.github/workflows/build_worker.yml (1)

171-171: LGTM: Correct context update for copier build.

The context change to root (.) aligns perfectly with:

• The PR objective
• The new Dockerfile structure that requires access to both server and worker modules
• The granular COPY commands in the Dockerfile