Update PR data Daily collection (2026-03-11T01:33:57Z)

[gounthar]

This PR contains automatically updated PR statistics data. Generated by GitHub Actions.

Summary by CodeRabbit

• Chores
  • Standardized plugin build configurations to support Java 11 and 17 runtime environments.
  • Updated Jenkins core version compatibility baseline for consistency across the plugin ecosystem.
  • Consolidated and simplified status tracking data for improved reporting clarity.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request automatically updates the daily collection of PR statistics data. Specifically, it prunes the failing_prs.json file by removing entries for pull requests that are no longer relevant, ensuring the dataset remains current and accurate.

Highlights

• Data Update: Removed outdated or resolved pull request entries from the failing_prs.json dataset.

Changelog

• data/consolidated/failing_prs.json
  • Removed three outdated pull request entries related to 'chore(github): Add CODEOWNERS', 'chore(dependencies): Automate dependency updates with Dependabot', and 'Applied recipe FixJellyIssues'.

Activity

• This pull request was automatically generated by GitHub Actions to update PR statistics data.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 62c31cd4-20b6-4f92-b095-f3e2d41a1344

📥 Commits

Reviewing files that changed from the base of the PR and between 75d10e9 and cc6374b.

📒 Files selected for processing (4)

• data/consolidated/all_prs.json
• data/consolidated/failing_prs.json
• data/consolidated/open_prs.json
• data/junit5/junit5_candidates.json

---

📝 Walkthrough

Walkthrough

These changes update consolidated JSON records for Jenkins plugin pull requests, standardizing Jenkins core and Java version requirements while cleaning up failing PR entries and resetting status check information in open PRs.

Changes

Cohort / File(s)	Summary
Jenkins Plugin PRs Data data/consolidated/all_prs.json	Added or updated Jenkins core version 2.462.3+ and Java 11/17 support configurations across multiple plugin PRs. Removed deprecated dependencies and outdated developer tags. Updated pom.xml references and BOM baseline properties for consistent dependency management.
Failing PRs Cleanup data/consolidated/failing_prs.json	Removed 129 lines of previously tracked failing PR entries, including CODEOWNERS additions and version/dependency update PRs with extensive descriptions.
Open PRs Status Reset data/consolidated/open_prs.json	Updated checkStatus field from "ERROR" to "UNKNOWN" across multiple entries. Simplified or cleared statusCheckRollup arrays, removing detailed individual check failure results and consolidating to success-only or empty states.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update PR data $(date +%Y-%m-%d) #48: Updates consolidated JSON PR data with checkStatus field changes and statusCheckRollup modifications.
• Update PR data Daily collection (2026-01-11T01:34:10Z) #327: Modifies consolidated JSON datasets (all_prs.json, failing_prs.json, open_prs.json) with PR metadata and status updates.
• Update PR data Daily collection (2025-10-04T01:13:24Z) #181: Updates consolidated JSON data files with statusCheckRollup conclusions and high-level checkStatus field changes.

Poem

🐰 Jenkins plugins hop with glee,
Core 2.462, Java 17!
Old checks fade to UNKNOWN grey,
Data cleaned, all's set for the day! 🔧✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch auto-update-pr-data

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Code Review

This pull request is an automated data update that removes three entries from data/consolidated/failing_prs.json. My review identifies a potential issue with this change. The removed pull requests appear to be in a failing state (ERROR), and other PRs with the same status remain in the file. This inconsistency suggests a possible bug in the data collection logic, making the current change questionable.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

I am having trouble creating individual review comments. Click here to see my feedback.

data/consolidated/failing_prs.json (5298-5426)

These pull requests are being removed, but they still appear to be in a failing state (checkStatus: "ERROR", state: "OPEN"). Other pull requests with the same checkStatus: "ERROR" are still present in this file. This inconsistent handling of PRs with an ERROR status suggests a potential issue in the data collection script. If ERROR is considered a failing state, these PRs should likely remain in this list.