chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Upgraded multiple plugins to their latest versions, enhancing overall performance, compatibility, and reliability. These updates ensure a smoother and more stable experience.

[coderabbitai]

Walkthrough

This pull request updates version numbers for several plugins in the dockerfiles/plugins.txt file. The modifications include minor increments across various plugins such as checks-api, configuration-as-code, credentials, pipeline-graph-view, pipeline-groovy-lib, pipeline-rest-api, pipeline-stage-view, ssh-slaves, sshd, token-macro, and workflow-support. Each update reflects routine maintenance and improvements in these plugins.

Changes

File	Change Summary
dockerfiles/plugins.txt	Updated plugin versions: checks-api (2.2.1 → 2.2.2), configuration-as-code (1929.v036b_5a_e1f123 → 1932.v75cb_b_f1b_698d), credentials (1405.vb_cda_74a_f8974 → 1408.va_622a_b_f5b_1b_1), pipeline-graph-view (406.v06871361eb_2d → 409.v98f212e980b_4), pipeline-groovy-lib (749.v70084559234a_ → 751.v709f84f7d768), and others.

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #289: Updates version numbers in dockerfiles/plugins.txt similar to this PR.
• chore(jenkins): Updates Jenkins plugins #304: Contains similar updates for configuration-as-code, credentials, and ssh-slaves plugins.
• chore(jenkins): Updates Jenkins plugins #277: Involves comprehensive plugin version updates in the dockerfiles/plugins.txt file.

Suggested labels

repo

Poem

I'm a hopping rabbit with a coder's beat,
Seeing plugin updates makes my heart skip a beat,
Each version bump is a carrot in sight,
Bringing freshness to our code day and night,
Hoppy upgrades and joyful glee,
Celebrating changes with a twitch of my ear and a spree!
🥕🐇

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

dockerfiles/plugins.txt (1)

12-12: Static Analysis – False Positives for Generic API Keys
The static analysis tool (Gitleaks) has flagged lines 12, 14, 51, 58, 61, and 63 as potential generic API keys. Since this file simply lists plugin names and their version numbers, these appear to be false positives. Consider suppressing these warnings or adding appropriate annotations if your tool supports it.

Also applies to: 14-14, 51-51, 58-58, 61-61, 63-63

🧰 Tools

🪛 Gitleaks (8.21.2)

12-12: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between ed1cc33 and 608bab0.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (3 hunks)

🧰 Additional context used

🪛 Gitleaks (8.21.2)

dockerfiles/plugins.txt

12-12: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

14-14: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

51-51: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

58-58: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

61-61: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

---

63-63: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Codacy Security Scan

🔇 Additional comments (11)

dockerfiles/plugins.txt (11)

9-9: Updated Version for checks-api Plugin
The checks-api plugin version has been updated to 2.2.2. Ensure that this minor update is compatible with your existing setup and review the plugin changelog for any subtle bug fixes or minor behavior changes.

---

13-13: Updated Version for configuration-as-code Plugin
The configuration-as-code plugin has been updated to version 1932.v75cb_b_f1b_698d. Please verify that your configuration files remain valid and that no deprecated features are being used with this new version.

---

15-15: Updated Version for credentials Plugin
The credentials plugin has been updated to 1408.va_622a_b_f5b_1b_1. It’s important to check that all credential storage and access mechanisms continue to function properly after this version bump.

---

47-47: Updated Version for pipeline-graph-view Plugin
The pipeline-graph-view plugin has been upgraded to version 409.v98f212e980b_4. Verify that any custom visualizations or integrations with Jenkins pipelines work as expected with this update.

---

48-48: Updated Version for pipeline-groovy-lib Plugin
The pipeline-groovy-lib plugin version is now 751.v709f84f7d768. Ensure that your pipeline scripts and groovy libraries remain compatible with any API changes introduced in this update.

---

54-54: Updated Version for pipeline-rest-api Plugin
The pipeline-rest-api plugin has been updated to 2.35. It is advisable to review the API changes and assess any potential impact on integrations that consume this plugin’s endpoints.

---

57-57: Updated Version for pipeline-stage-view Plugin
The pipeline-stage-view plugin is now version 2.35. Please verify that any customizations or plugins that interact with stage views are not adversely affected by this change.

---

65-65: Updated Version for ssh-slaves Plugin
The ssh-slaves plugin has been updated to 3.1031.v72c6b_883b_869. Ensure that agent connections relying on SSH continue to work correctly, and review any related security settings.

---

66-66: Updated Version for sshd Plugin
The sshd plugin version is updated to 3.350.v1080103a_10fd. Double-check SSH daemon functionalities and its security configuration to ensure no disruptions occur following the upgrade.

---

69-69: Updated Version for token-macro Plugin
The token-macro plugin now uses version 444.v52de7e9c573d. Confirm that token expansions and related job configurations continue to operate as previously expected after the update.

---

81-81: Updated Version for workflow-support Plugin
The workflow-support plugin has been updated to 946.v2a_79d8a_4b_e14. It is recommended to run tests on pipeline jobs and workflow processing to validate that the update does not introduce any breaking changes.