[CI] Remove Jenkins PR linter step#19795
Conversation
The Jenkins PR title/body linter is comparatively heavy and can report false positives before the normal CI signal is available. This removes the check_pr step from the Jenkins prepare flow and drops the now-unused script-level test coverage.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request removes the PR title and body linter check (check_pr.py) from the Jenkins CI pipeline. This includes deleting the check_pr.py script, removing the check_pr helper function and its invocation from the Jenkinsfile templates and generated Jenkinsfiles, and removing the corresponding unit tests in test_ci.py. There are no review comments to assess, and I have no further feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
Replaced by #19798 from an apache/tvm branch because this change touches generated Jenkinsfiles. |
1 participant
Summary
The Jenkins PR title/body linter can be comparatively heavy and can report false positives before the normal CI signal is available. This PR removes that Jenkins prepare-flow check so PR validation proceeds through the remaining CI jobs.
Changes
check_prinvocation from all Jenkins pipelines.