Skip to content

Conversation

tanmayv25
Copy link
Contributor

@tanmayv25 tanmayv25 commented Aug 15, 2025

Overview:

Missed renaming the dockerfile here

Summary by CodeRabbit

  • Chores
    • Updated CI path filters to align with a renamed component, ensuring the correct pipelines trigger for relevant container changes.
    • Improves reliability and accuracy of automated build triggers for the TRT LLM group.
  • Notes
    • No user-facing functionality or UI changes.
    • Existing workflow logic and other triggers remain unchanged.

@tanmayv25 tanmayv25 requested review from nnshah1 and a team as code owners August 15, 2025 23:27
@tanmayv25 tanmayv25 changed the title Fix the Dockerfile name fix: Fix the Dockerfile name Aug 15, 2025
@github-actions github-actions bot added the fix label Aug 15, 2025
Copy link
Contributor

coderabbitai bot commented Aug 15, 2025

Walkthrough

Updates the trtllm path filter in .github/workflows/trigger_ci.yml from container/Dockerfile.tensorrt_llm to container/Dockerfile.trtllm so that changes to the new Dockerfile trigger src_changes.trtllm and RUN_TRTLLM. No other workflow logic or filters were modified.

Changes

Cohort / File(s) Summary of Changes
Workflow path filter update
.github/workflows/trigger_ci.yml
Renamed path filter target from container/Dockerfile.tensorrt_llm to container/Dockerfile.trtllm; ensures changes set src_changes.trtllm: true and enable RUN_TRTLLM. No other triggers/logic changed.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant GH as GitHub Actions
  participant WF as trigger_ci.yml
  participant PIPE as Trigger Pipeline

  Dev->>GH: Push/PR with file changes
  GH->>WF: Evaluate path filters
  alt Dockerfile.trtllm changed
    WF->>WF: Set src_changes.trtllm = true
    WF->>PIPE: Enable RUN_TRTLLM
  else No relevant change
    WF->>PIPE: RUN_TRTLLM not enabled
  end
Loading

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Poem

A hop to the left, a path set right,
I twitch my nose at CI’s new light.
TRT-LLM hears the call—
New Dockerfile, no missed ball.
Pipelines hum, carrots cheer,
Green checks blossom: spring is here! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.


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
🪧 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
.github/workflows/trigger_ci.yml (1)

55-61: Consider temporarily including the legacy Dockerfile path for forward/backward compatibility

If any long-lived branches or pending PRs still reference the old Dockerfile.tensorrt_llm, CI won’t trigger for TRT LLM changes on those branches. You can include both paths short-term to avoid blind spots.

Apply this minimal additive change:

 trtllm:
+  - 'container/Dockerfile.tensorrt_llm'
   - 'container/Dockerfile.trtllm'
   - 'components/backends/trtllm/**'
   - 'container/build.sh'
   - 'container/build_trtllm_wheel.sh'
   - 'container/deps/**'
   - 'tests/serve/test_trtllm.py'
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 922850a and 2591c4a.

📒 Files selected for processing (1)
  • .github/workflows/trigger_ci.yml (1 hunks)
⏰ 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 and Test - dynamo
🔇 Additional comments (2)
.github/workflows/trigger_ci.yml (2)

55-55: Path filter rename looks correct and aligns with PR intent

Switching to 'container/Dockerfile.trtllm' matches the stated Dockerfile rename and will properly flip src_changes.trtllm for RUN_TRTLLM.


55-61: ✅ New TRT LLM Dockerfile present & no legacy references found
All checks passed:

  • container/Dockerfile.trtllm (and its prebuilt variant) exists
  • No occurrences of Dockerfile.tensorrt_llm remain in the repo or workflows

No further action needed.

@tanmayv25 tanmayv25 enabled auto-merge (squash) August 15, 2025 23:32
@tanmayv25 tanmayv25 merged commit 0a1168c into main Aug 15, 2025
10 of 12 checks passed
@tanmayv25 tanmayv25 deleted the tanmayv-wf branch August 15, 2025 23:52
hhzhang16 pushed a commit that referenced this pull request Aug 27, 2025
Signed-off-by: Hannah Zhang <hannahz@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants