FDSF-262: Adjust build process to target version.

[adam-vessey]

The branch has gotten another release; however, we are not yet ready to move up to it (it's being tracked elsewhere, i.e.: #17 ).

Building against discoverygarden/cantaloupe_configs#19 , with something like:

docker build --build-arg CANTALOUPE_CONFIGS_VERSION=feature/redirect-header-control -t 358734507516.dkr.ecr.us-east-1.amazonaws.com/cantaloupe:fdsf-262 --push --platform=linux/arm64,linux/amd64 .

Summary by CodeRabbit

• Chores
  • Streamlined the container build process by switching from a branch-based dependency retrieval approach to a version-specific method. This improvement simplifies resource acquisition and ensures a more consistent, reliable build workflow without altering user-facing functionality.

[coderabbitai]

Walkthrough

The Dockerfile has been updated to remove the CANTALOUPE_BRANCH argument and its associated cloning method. In its place, a new argument, CANTALOUPE_VERSION, is introduced. Instead of using git clone to fetch the repository using a branch, the repository is now added directly using the ADD command with the specified version tag. Additionally, the working directory is set to /build/cantaloupe to ensure subsequent commands run in the correct context.

Changes

File	Change Summary
Dockerfile	Removed ARG CANTALOUPE_BRANCH; added ARG CANTALOUPE_VERSION; replaced the git clone command with an ADD command that references the repository via a version tag; set working directory to /build/cantaloupe

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant Docker as Docker Build Process
    participant Repo as Cantaloupe Repository

    Dev->>Docker: Build with ARG CANTALOUPE_VERSION
    Docker->>Repo: ADD repository with version tag
    Repo-->>Docker: Repository content received
    Docker->>Docker: Set WORKDIR to /build/cantaloupe

Loading

Poem

In the Docker world, a change so fine,
Old branches fade as new versions shine.
No more clone, the code hops into view,
With a swift ADD, the build stays true.
I'm a happy rabbit, skipping down the line—
Code so clear, it's utterly divine!
🐇🌟

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (1)

• JIRA integration encountered authorization issues. Please disconnect and reconnect the integration in the CodeRabbit UI.

---

📜 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 8773990 and bcf0404.

📒 Files selected for processing (1)

• Dockerfile (1 hunks)

🧰 Additional context used

🪛 Hadolint (2.12.0)

Dockerfile

[error] 37-37: Use COPY instead of ADD for files and folders

(DL3020)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build / build-push

🔇 Additional comments (2)

Dockerfile (2)

28-30: New ARG CANTALOUPE_VERSION looks good

Replacing the former CANTALOUPE_BRANCH with an explicit CANTALOUPE_VERSION cleanly expresses the intent to pin to a release tag. This improves reproducibility and removes the ambiguity that comes with pointing at a moving branch.

---

37-40: ADD --link …#v$CANTALOUPE_VERSION requires BuildKit – ensure builders enable it

ADD --link with a remote Git URL is only supported when Docker BuildKit is enabled. If this image is ever built on classic builders (e.g., CI workers still on legacy Docker or Kaniko without BuildKit-Git support), the build will fail at this step.

Consider documenting the requirement (e.g., DOCKER_BUILDKIT=1) in your build docs/CI config, or fall back to a plain git clone guarded by a build-arg switch.

No action needed if all build environments are confirmed BuildKit-ready.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

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.