chore(jenkins): Updates Jenkins plugins

[gounthar]

This pull request updates the Jenkins plugins listed in plugins.txt.

Summary by CodeRabbit

• Chores
  • Updated version numbers for various plugins to maintain current standards.

[coderabbitai]

Walkthrough

This pull request involves updating plugin versions in the dockerfiles/plugins.txt file. The changes are primarily focused on incrementing version numbers for various Jenkins plugins, including notable updates to the cloudbees-folder plugin from version 6.971.v9a_984fd08864 to 6.973.vc9b_85a_61e4fc and the gradle plugin from 2.13.1 to 2.14. These updates represent a routine maintenance effort to keep the plugin ecosystem current.

Changes

File	Change Summary
dockerfiles/plugins.txt	Updated plugin versions, including cloudbees-folder and gradle

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #265: Updates to plugin versions in dockerfiles/plugins.txt
• chore(jenkins): Updates Jenkins plugins #267: Similar plugin version number updates
• chore(jenkins): Updates Jenkins plugins #276: Maintenance updates to plugin versions
• chore(jenkins): Updates Jenkins plugins #277: Update to cloudbees-folder plugin version
• chore(jenkins): Updates Jenkins plugins #278: Another cloudbees-folder plugin version update
• chore(jenkins): Updates Jenkins plugins #288: Previous cloudbees-folder plugin version update

Suggested labels

repo

Poem

🐰 Plugins dancing, versions bright
Updating with systematic might
From old to new, a gentle leap
Keeping our Jenkins ecosystem deep
A rabbit's touch of maintenance delight! 🔧

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. This feature will be included in our Pro Plan when released.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fd73327 and dcb9e96.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (2 hunks)

✅ Files skipped from review due to trivial changes (1)

• dockerfiles/plugins.txt

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.