[None][infra] Remove PULSE_REPO_BRANCH when running source code scanning#13778
Conversation
It is not needed if we don't want to overrid nspect report Signed-off-by: Yuanjing Xue <197832395+yuanjingx87@users.noreply.github.com>
📝 WalkthroughWalkthroughThe pull request removes the PULSE_REPO_BRANCH environment variable from the Pulse scanning step in the Jenkins TensorRT LLM pipeline configuration. This eliminates conditional logic that previously differentiated between fork and non-fork repository branch references. ChangesJenkins Pipeline Configuration
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Comment |
|
/bot skip --comment "No need to run CI" |
|
PR_Github #46864 [ skip ] triggered by Bot. Commit: |
|
PR_Github #46864 [ skip ] completed with state |
…ing (NVIDIA#13778) Signed-off-by: Yuanjing Xue <197832395+yuanjingx87@users.noreply.github.com>
It is not needed if we don't want to overrid nspect report
@coderabbitai summary
Description
Source code scanning might fail due to "nSpect verification returned 404 (Not Found) for NSPECT ID ***"
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
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
To see a list of available CI bot commands, please comment
/bot help.