[TRTLLMINF-9][chore] Remove submodule pulls from TRT-LLM git checkouts

[dpitman-nvda]

Summary by CodeRabbit

• Chores
  • Updated CI/CD pipeline configuration to refine source checkout behavior during build and test processes.

Description

TRT-LLM pulls submodules during git checkouts, but according to our sources, we do not have submodules in the repo any more and this flag adds noise to the Jenkins runs.

Updating the Jenkins groovy files to disable fetching submodules across all CI workflows.

Test Coverage

N/A, this is in CI

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

• Update tava architecture diagram if there is a significant design change in PR.

• 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.

Details

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

Across two Jenkins Groovy pipeline files, calls to trtllm_utils.checkoutSource have their first boolean parameter changed from true to false, affecting source checkout behavior during merge request validation and test execution.

Changes

Cohort / File(s)	Summary
Jenkins Pipeline Configuration jenkins/L0_MergeRequest.groovy, jenkins/L0_Test.groovy	Modified checkoutSource calls to pass false (instead of true) for the first boolean parameter in collectTestResults and runLLMDocBuild/LLMAPI execution paths, while preserving the second boolean parameter as true.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title directly and accurately describes the main change: disabling submodule pulls from git checkouts in CI workflows, which matches the PR's primary objective.
Description check	✅ Passed	PR description clearly explains the issue and solution, with proper ticket format [TRTLLMINF-9][chore] and appropriate test coverage rationale for CI changes.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

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

---

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

[dpitman-nvda]

/bot run

[tensorrt-cicd]

PR_Github #36822 [ run ] triggered by Bot. Commit: 0b944fb Link to invocation

[tburt-nv]

/bot run

[tensorrt-cicd]

PR_Github #36830 [ run ] triggered by Bot. Commit: dc24778 Link to invocation

[tensorrt-cicd]

PR_Github #36830 [ run ] completed with state SUCCESS. Commit: dc24778
/LLM/main/L0_MergeRequest_PR pipeline #28518 completed with status: 'FAILURE'

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

[dpitman-nvda]

/bot run

[tensorrt-cicd]

PR_Github #36954 [ run ] triggered by Bot. Commit: 7df4b79 Link to invocation

[tensorrt-cicd]

PR_Github #36954 [ run ] completed with state SUCCESS. Commit: 7df4b79
/LLM/main/L0_MergeRequest_PR pipeline #28615 completed with status: 'FAILURE'

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

Link to invocation

[dpitman-nvda]

/bot run

[tensorrt-cicd]

PR_Github #37088 [ run ] triggered by Bot. Commit: 7df4b79 Link to invocation

[tensorrt-cicd]

PR_Github #37088 [ run ] completed with state SUCCESS. Commit: 7df4b79
/LLM/main/L0_MergeRequest_PR pipeline #28716 completed with status: 'SUCCESS'

Link to invocation