[TRTLLMINF-420][fix] Add Jenkins instance name to SLURM job

[lyxxn0414]

Dev Engineer Review

getJenkinsInstanceName() derives the instance name from JENKINS_URL or Jenkins.instance.rootUrl, then removes trailing slashes. Both SLURM execution paths include this name in their lower-case suffix with BUILD_TAG and a six-character random identifier. No material source risks were identified.

QA Engineer Review

No test changes.

Per-File QA Perspective

• jenkins/L0_Test.groovy: Verify job, node, workspace, log, and generated script names across all Jenkins instances. Verify behavior when the instance name comes from either supported URL source.

Description

Sub test jobs now run on four downstream Jenkins instances (github-1..4) instead of a single one. This adds the Jenkins instance name to the unique suffix on both SLURM submission paths:

• runLLMTestlistWithSbatch
• runLLMTestlistWithAgent

Test Coverage

SLURM job name:

SLURM output log file name:

The UNSTABLE is just the multi-GPU ci: full pre-merge approved label gate, not a test failure.

PR Checklist

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

[lyxxn0414]

/bot run --stage-list "DGX_B200-CPP-1,DGX_H100-2_GPUs-PyTorch-GptOss-1"

[tensorrt-cicd]

PR_Github #74054 [ run ] triggered by Bot. Commit: ff674d3 Link to invocation

[tensorrt-cicd]

PR_Github #74054 [ run ] completed with state SUCCESS. Commit: ff674d3
/LLM/main/L0_MergeRequest_PR pipeline #60896 (Partly Tested) completed with status: 'UNSTABLE'

CI Report

⚠️ Multi-GPU Label Required:
Multi-GPU tests require the ci: full pre-merge approved label on this PR. Either:

• Ask a member of NVIDIA/trt-llm-ci-approvers to add the label, or
• Wait for the PR to be fully approved — the label is added automatically once approval is complete.
  Then re-trigger CI with the same bot command (no rebase needed).

⚠️ 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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6b4124db-aee7-46cc-b595-2885b1fef6d5

📥 Commits

Reviewing files that changed from the base of the PR and between 9d0a788 and 4f287b8.

📒 Files selected for processing (1)

• jenkins/L0_Test.groovy

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

Walkthrough

The Jenkins pipeline adds a helper that derives the Jenkins instance name from configured URLs. SLURM agent and multi-node job suffixes now include this name before the build tag and random identifier.

Changes

Jenkins-aware SLURM naming

Layer / File(s)	Summary
Instance-aware SLURM suffixes jenkins/L0_Test.groovy	The pipeline derives the Jenkins instance name and includes it in SLURM agent and multi-node job suffixes.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Bug fix

Suggested reviewers: brnguyen2

Merge Risk: ⚪ Minimal · up to 4f287

The change adds the Jenkins instance token to both relevant SLURM suffixes, and no established failure remains that should block merging.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the fix and matches the main change: adding the Jenkins instance name to SLURM job identifiers. It also follows the required ticket and type format.
Description check	✅ Passed	The description explains the problem, identifies both affected submission paths, and provides test coverage evidence. It includes the required Description, Test Coverage, and PR Checklist sections. So…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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