Update PR data Daily collection (2026-05-17T02:27:10Z)#490
Merged
Conversation
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis PR updates consolidated CI status data across three JSON datasets. It reclassifies six plugin PRs from ERROR to UNKNOWN status, removes associated error check contexts, refreshes dtkit-plugin's security check rollup records, and replaces entries in the failing PR dataset. ChangesPR Data Status Consolidation
Possibly related PRs
Poem
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the consolidated PR data by removing several entries from failing_prs.json and cleaning up status check information in open_prs.json. Feedback focuses on a recurring issue in open_prs.json where the checkStatus for multiple plugins was changed to "UNKNOWN" despite the statusCheckRollup still containing failed check runs. The reviewer suggests maintaining the "ERROR" status to accurately reflect the state of these pull requests.
| "url": "https://github.com/jenkinsci/osf-builder-suite-for-sfcc-run-job-plugin/pull/11", | ||
| "description": "Hello osf-builder-suite-for-sfcc-run-job developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.462.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.462.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "ERROR", | ||
| "checkStatus": "UNKNOWN", |
Contributor
There was a problem hiding this comment.
The checkStatus is being changed to "UNKNOWN" despite the statusCheckRollup still containing a CheckRun with a "FAILURE" conclusion (see line 4702). This suggests a bug in the status aggregation logic where removing the StatusContext (which previously held the "ERROR" state) causes the overall status to be lost instead of being derived from the remaining CheckRun.
Suggested change
| "checkStatus": "UNKNOWN", | |
| "checkStatus": "ERROR", |
| "url": "https://github.com/jenkinsci/portscanner-plugin/pull/3", | ||
| "description": "Hello portscanner developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.462.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.462.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "ERROR", | ||
| "checkStatus": "UNKNOWN", |
Contributor
There was a problem hiding this comment.
The checkStatus is being changed to "UNKNOWN" despite the statusCheckRollup still containing a CheckRun with a "FAILURE" conclusion (see line 4922). This suggests a bug in the status aggregation logic where removing the StatusContext causes the overall status to be lost.
Suggested change
| "checkStatus": "UNKNOWN", | |
| "checkStatus": "ERROR", |
| "url": "https://github.com/jenkinsci/project-description-setter-plugin/pull/3", | ||
| "description": "Hello project-description-setter developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.462.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.462.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "ERROR", | ||
| "checkStatus": "UNKNOWN", |
Contributor
There was a problem hiding this comment.
The checkStatus is being changed to "UNKNOWN" despite the statusCheckRollup still containing a CheckRun with a "FAILURE" conclusion (see line 4948). This suggests a bug in the status aggregation logic where removing the StatusContext causes the overall status to be lost.
Suggested change
| "checkStatus": "UNKNOWN", | |
| "checkStatus": "ERROR", |
| "url": "https://github.com/jenkinsci/vstestrunner-plugin/pull/85", | ||
| "description": "Hello vstestrunner developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.462.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.462.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "ERROR", | ||
| "checkStatus": "UNKNOWN", |
Contributor
There was a problem hiding this comment.
The checkStatus is being changed to "UNKNOWN" despite the statusCheckRollup still containing a CheckRun with a "FAILURE" conclusion (see line 7577). This suggests a bug in the status aggregation logic where removing the StatusContext causes the overall status to be lost.
Suggested change
| "checkStatus": "UNKNOWN", | |
| "checkStatus": "ERROR", |
| "url": "https://github.com/jenkinsci/winrm-client-plugin/pull/10", | ||
| "description": "Hello winrm-client developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.462.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.462.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "ERROR", | ||
| "checkStatus": "UNKNOWN", |
Contributor
There was a problem hiding this comment.
The checkStatus is being changed to "UNKNOWN" despite the statusCheckRollup still containing a CheckRun with a "FAILURE" conclusion (see line 7738). This suggests a bug in the status aggregation logic where removing the StatusContext causes the overall status to be lost.
Suggested change
| "checkStatus": "UNKNOWN", | |
| "checkStatus": "ERROR", |
| "url": "https://github.com/jenkinsci/xooa-plugin/pull/3", | ||
| "description": "Hello xooa developers! 👋\nThis is an automated pull request created by the Jenkins Plugin Modernizer tool. The tool has applied the following recipes to modernize the plugin:\n\n Upgrade to the latest recommended core version and ensure the BOM matches the core version\n io.jenkins.tools.pluginmodernizer.UpgradeToRecommendCoreVersion\n Upgrade to the latest recommended core version and ensure the BOM matches the core version.\n\nWhy is this important?\nJenkins plugins declare a minimum supported Jenkins version.\nThe minimum Jenkins version is a useful way for plugin developers to indicate the range of Jenkins versions they are willing to support and test.\nSee the developer documentation to learn more about the recommended minimum Jenkins version.\nThe current minimum required Jenkins version is 2.462.3, which is why this pull request has been made.\nIf the plugin is already using the plugin bill of materials, then the bill of materials also needs to be updated with the matching artifactId for the minimum required Jenkins version.\nI can't see any change to the Jenkins version, how come?\nThis means your plugin POM was already using the 2.462.3 version but still required a few adjustments.\nThe checks fail, why?\nFor security reasons, the Jenkins infrastructure does not execute Jenkinsfiles proposed in pull requests.\nInstead, it builds the code using the Jenkinsfile from the default branch.\nIn this case, the existing Jenkinsfile specifies Java 8, not Java 11, which is causing the check to fail.\nTo resolve this,\na maintainer can replay the failed build\nby substituting the current Jenkinsfile content with our proposed changes using the \"replay the build\"\nfeature in Jenkins.\nPlease let us know if you need any assistance with this process.\nThanks for taking the time to review this PR.\n🙏", | ||
| "checkStatus": "ERROR", | ||
| "checkStatus": "UNKNOWN", |
Contributor
There was a problem hiding this comment.
The checkStatus is being changed to "UNKNOWN" despite the statusCheckRollup still containing a CheckRun with a "FAILURE" conclusion (see line 7869). This suggests a bug in the status aggregation logic where removing the StatusContext causes the overall status to be lost.
Suggested change
| "checkStatus": "UNKNOWN", | |
| "checkStatus": "ERROR", |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains automatically updated PR statistics data. Generated by GitHub Actions.
Summary by CodeRabbit