[DO NOT MERGE] -- Test inline check PR comment#4374
Conversation
Signed-off-by: Miguel Dalberto Pedro <miguel.pedro@precisioninno.com>
There was a problem hiding this comment.
Code Review
This pull request updates the Jenkinsfile to use a feature branch ('inline-check-pr-comment') for the shared library instead of the 'main' branch. The feedback advises reverting this change to a stable branch or version tag before merging to avoid potential pipeline failures if the feature branch is modified or deleted.
| @@ -1,4 +1,4 @@ | |||
| @Library('utils@main') _ | |||
| @Library('utils@inline-check-pr-comment') _ | |||
There was a problem hiding this comment.
Referencing a feature branch ('inline-check-pr-comment') for the shared library is acceptable for testing, but it should be reverted to a stable branch (such as 'main') or a specific version tag before merging. This prevents pipeline failures if the feature branch is deleted or modified in the future.
@Library('utils@main') _
🔍 QoR checkMetrics reflect the PR merge build — i.e. what will land on the target branch. Advisory — results are log-only and do not affect build status. The authoritative QoR gate remains the local rules-file check. Commit 57 design(s) checked — 0 with regression(s), 0 without a baseline.
|
No description provided.