[TRTLLM-9080][infra] upgrade tritonserver DLFW 25.10

[ZhanruiSunCh]

Summary by CodeRabbit

• Chores
  • Updated Triton framework version from 25.09 to 25.10 across all infrastructure components. This includes updates to Docker base image configuration, the build pipeline repository references, and test infrastructure version specifications. The changes ensure consistent Triton version alignment throughout the entire build, testing, and deployment pipeline, maintaining compatibility across all systems.

Description

Test Coverage

PR Checklist

Please review the following before submitting your PR:

• PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

• PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

• Test cases are provided for new code paths (see test instructions)

• Any new dependencies have been scanned for license and vulnerabilities

• CODEOWNERS updated if ownership changes

• Documentation updated as needed

• The reviewers assigned automatically/manually are appropriate for the PR.

• Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

/bot [-h] ['run', 'kill', 'skip', 'reuse-pipeline'] ...

Provide a user friendly way for developers to interact with a Jenkins server.

Run /bot [-h|--help] to print this help message.

See details below for each supported subcommand.

run [--reuse-test (optional)pipeline-id --disable-fail-fast --skip-test --stage-list "A10-PyTorch-1, xxx" --gpu-type "A30, H100_PCIe" --test-backend "pytorch, cpp" --add-multi-gpu-test --only-multi-gpu-test --disable-multi-gpu-test --post-merge --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" --detailed-log --debug(experimental)]

Launch build/test pipelines. All previously running jobs will be killed.

--reuse-test (optional)pipeline-id (OPTIONAL) : Allow the new pipeline to reuse build artifacts and skip successful test stages from a specified pipeline or the last pipeline if no pipeline-id is indicated. If the Git commit ID has changed, this option will be always ignored. The DEFAULT behavior of the bot is to reuse build artifacts and successful test results from the last pipeline.

--disable-reuse-test (OPTIONAL) : Explicitly prevent the pipeline from reusing build artifacts and skipping successful test stages from a previous pipeline. Ensure that all builds and tests are run regardless of previous successes.

--disable-fail-fast (OPTIONAL) : Disable fail fast on build/tests/infra failures.

--skip-test (OPTIONAL) : Skip all test stages, but still run build stages, package stages and sanity check stages. Note: Does NOT update GitHub check status.

--stage-list "A10-PyTorch-1, xxx" (OPTIONAL) : Only run the specified test stages. Examples: "A10-PyTorch-1, xxx". Note: Does NOT update GitHub check status.

--gpu-type "A30, H100_PCIe" (OPTIONAL) : Only run the test stages on the specified GPU types. Examples: "A30, H100_PCIe". Note: Does NOT update GitHub check status.

--test-backend "pytorch, cpp" (OPTIONAL) : Skip test stages which don't match the specified backends. Only support [pytorch, cpp, tensorrt, triton]. Examples: "pytorch, cpp" (does not run test stages with tensorrt or triton backend). Note: Does NOT update GitHub pipeline status.

--only-multi-gpu-test (OPTIONAL) : Only run the multi-GPU tests. Note: Does NOT update GitHub check status.

--disable-multi-gpu-test (OPTIONAL) : Disable the multi-GPU tests. Note: Does NOT update GitHub check status.

--add-multi-gpu-test (OPTIONAL) : Force run the multi-GPU tests in addition to running L0 pre-merge pipeline.

--post-merge (OPTIONAL) : Run the L0 post-merge pipeline instead of the ordinary L0 pre-merge pipeline.

--extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx" (OPTIONAL) : Run the ordinary L0 pre-merge pipeline and specified test stages. Examples: --extra-stage "H100_PCIe-TensorRT-Post-Merge-1, xxx".

--detailed-log (OPTIONAL) : Enable flushing out all logs to the Jenkins console. This will significantly increase the log volume and may slow down the job.

--debug (OPTIONAL) : Experimental feature. Enable access to the CI container for debugging purpose. Note: Specify exactly one stage in the stage-list parameter to access the appropriate container environment. Note: Does NOT update GitHub check status.

For guidance on mapping tests to stage names, see docs/source/reference/ci-overview.md
and the scripts/test_to_stage_mapping.py helper.

kill

kill

Kill all running builds associated with pull request.

skip

skip --comment COMMENT

Skip testing for latest commit on pull request. --comment "Reason for skipping build/test" is required. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

reuse-pipeline

reuse-pipeline

Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break.

[ZhanruiSunCh]

/bot run --stage-list "Build-Docker-Images"

[coderabbitai]

📝 Walkthrough

Walkthrough

Three configuration files updated to reference Triton version 25.10 instead of 25.09. Changes include updating the Docker base image tag, the Jenkins build repository tag, and the test server version parameter. No logic or control flow modifications.

Changes

Cohort / File(s)	Summary
Triton version update docker/Dockerfile.multi, jenkins/Build.groovy, jenkins/L0_Test.groovy	Updated Triton version references from 25.09 to 25.10 across Docker configuration and Jenkins pipeline files. TRITON_BASE_TAG updated in Dockerfile, repository tag updated in Build.groovy cmake configuration, and NVIDIA_TRITON_SERVER_VERSION parameter updated in L0_Test.groovy.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is incomplete and does not follow the repository's template properly. While the template is present in the PR body, the critical sections—Description, Test Coverage, and substantive PR Checklist items—are left empty or unchecked. The author has not provided any explanation of what the changes accomplish, why the upgrade is necessary, or what tests validate the version bump.	Please fill in the Description section explaining the rationale for upgrading to Triton 25.10, specify the Test Coverage section by listing which tests (e.g., L0 tests, build validation) confirm the upgrade works correctly, and complete the PR Checklist by checking the box once all items are addressed. Even if using CodeRabbit's summary feature, please ensure the description clearly communicates the purpose and testing strategy for this infrastructure change.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title '[TRTLLM-9080][infra] upgrade tritonserver DLFW 25.10' clearly and specifically describes the main change in the changeset. It follows the repository's template pattern with the JIRA ticket identifier and type label. The title accurately reflects the core changes: upgrading the Triton server version from 25.09 to 25.10 across multiple configuration files (Dockerfile, Build.groovy, and L0_Test.groovy).

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e9e1a36 and 46946e6.

📒 Files selected for processing (3)

• docker/Dockerfile.multi (1 hunks)
• jenkins/Build.groovy (1 hunks)
• jenkins/L0_Test.groovy (1 hunks)

🧰 Additional context used

🧠 Learnings (6)

📚 Learning: 2025-08-18T09:08:07.687Z

Learnt from: tongyuantongyu
Repo: NVIDIA/TensorRT-LLM PR: 6984
File: cpp/tensorrt_llm/CMakeLists.txt:297-299
Timestamp: 2025-08-18T09:08:07.687Z
Learning: In the TensorRT-LLM project, artifacts are manually copied rather than installed via `cmake --install`, so INSTALL_RPATH properties are not needed - only BUILD_RPATH affects the final artifacts.

Applied to files:

• jenkins/Build.groovy

📚 Learning: 2025-08-06T13:58:07.506Z

Learnt from: galagam
Repo: NVIDIA/TensorRT-LLM PR: 6487
File: tests/unittest/_torch/auto_deploy/unit/singlegpu/test_ad_trtllm_bench.py:1-12
Timestamp: 2025-08-06T13:58:07.506Z
Learning: In TensorRT-LLM, test files (files under tests/ directories) do not require NVIDIA copyright headers, unlike production source code files. Test files typically start directly with imports, docstrings, or code.

Applied to files:

• jenkins/L0_Test.groovy

📚 Learning: 2025-09-09T09:40:45.658Z

Learnt from: fredricz-20070104
Repo: NVIDIA/TensorRT-LLM PR: 7645
File: tests/integration/test_lists/qa/llm_function_core.txt:648-648
Timestamp: 2025-09-09T09:40:45.658Z
Learning: In TensorRT-LLM test lists, it's common and intentional for the same test to appear in multiple test list files when they serve different purposes (e.g., llm_function_core.txt for comprehensive core functionality testing and llm_function_core_sanity.txt for quick sanity checks). This duplication allows tests to be run in different testing contexts.

Applied to files:

• jenkins/L0_Test.groovy

📚 Learning: 2025-08-11T20:09:24.389Z

Learnt from: achartier
Repo: NVIDIA/TensorRT-LLM PR: 6763
File: tests/integration/defs/triton_server/conftest.py:16-22
Timestamp: 2025-08-11T20:09:24.389Z
Learning: In the TensorRT-LLM test infrastructure, the team prefers simple, direct solutions (like hard-coding directory traversal counts) over more complex but robust approaches when dealing with stable directory structures. They accept the maintenance cost of updating tests if the layout changes.

Applied to files:

• jenkins/L0_Test.groovy

📚 Learning: 2025-07-28T17:06:08.621Z

Learnt from: moraxu
Repo: NVIDIA/TensorRT-LLM PR: 6303
File: tests/integration/test_lists/qa/examples_test_list.txt:494-494
Timestamp: 2025-07-28T17:06:08.621Z
Learning: In TensorRT-LLM testing, it's common to have both CLI flow tests (test_cli_flow.py) and PyTorch API tests (test_llm_api_pytorch.py) for the same model. These serve different purposes: CLI flow tests validate the traditional command-line workflow, while PyTorch API tests validate the newer LLM API backend. Both are legitimate and should coexist.

Applied to files:

• jenkins/L0_Test.groovy

📚 Learning: 2025-08-01T15:14:45.673Z

Learnt from: yibinl-nvidia
Repo: NVIDIA/TensorRT-LLM PR: 6506
File: examples/models/core/mixtral/requirements.txt:3-3
Timestamp: 2025-08-01T15:14:45.673Z
Learning: In TensorRT-LLM, examples directory can have different dependency versions than the root requirements.txt file. Version conflicts between root and examples dependencies are acceptable because examples are designed to be standalone and self-contained.

Applied to files:

• jenkins/L0_Test.groovy

⏰ 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: Pre-commit Check

🔇 Additional comments (3)

docker/Dockerfile.multi (1)

5-5: LGTM!

The Triton base tag update is consistent with the version upgrade across the codebase.

jenkins/L0_Test.groovy (1)

1100-1100: LGTM!

The Triton server version update in the test environment variable is consistent with the infrastructure upgrade to version 25.10.

jenkins/Build.groovy (1)

456-458: Triton version r25.10 is valid and available.

The version is confirmed in official NVIDIA release notes (release 25.10), and the NGC container is available with this release tag. No breaking changes block this upgrade.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[tensorrt-cicd]

PR_Github #23372 [ run ] triggered by Bot. Commit: 46946e6

[ZhanruiSunCh]

/bot run --stage-list "Build-Docker-Images"

[tensorrt-cicd]

PR_Github #23468 [ run ] triggered by Bot. Commit: 2f5b80c

[ZhanruiSunCh]

/bot run --disable-fail-fast --post-merge

[tensorrt-cicd]

PR_Github #23486 [ run ] triggered by Bot. Commit: e6d9ce4

[tensorrt-cicd]

PR_Github #23468 [ run ] completed with state ABORTED. Commit: 2f5b80c
LLM/release-1.1/L0_MergeRequest_PR #398 (Blue Ocean) completed with status: ABORTED