chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Upgraded several system plugins to their latest versions, enhancing underlying performance and reliability for an improved user experience.

[coderabbitai]

Walkthrough

This pull request updates plugin version numbers in a configuration file. The changes involve incrementing version numbers for multiple plugins listed in the dockerfiles/plugins.txt file. Each plugin has been updated from its previous version to a newer one. These modifications reflect systematic version bumps across the plugins without any alterations to the underlying control flow or functionality.

Changes

File	Change Summary
dockerfiles/plugins.txt	Updated version numbers for plugins: apache-httpcomponents-client-4-api, checks-api, configuration-as-code, credentials, junit, pipeline-build-step, pipeline-graph-view, pipeline-rest-api, pipeline-stage-view, ssh-slaves, sshd, token-macro, workflow-cps, workflow-job, workflow-support.

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #277: Direct updates to multiple plugins in dockerfiles/plugins.txt indicate a strong code-level connection.
• chore(jenkins): Updates Jenkins plugins #278: Involves updating the junit plugin version, closely mirroring changes made in this PR.
• chore(jenkins): Updates Jenkins plugins #304: Updates several plugins including configuration-as-code, credentials, ssh-slaves, and workflow-cps, showing a direct file-level modification.

Suggested labels

repo

Poem

Hopping through code with joyful glee,
My whiskers twitch at each update I see.
Plugin versions leap to a brand new day,
In dockerfiles magic, I dance and play.
With ASCII hops and a cheerful nod,
This rabbit sings change with a happy applaud! 🐇

---

📜 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 ed1cc33 and 6d09fe6.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (3 hunks)

🧰 Additional context used

🪛 Gitleaks (8.21.2)

dockerfiles/plugins.txt

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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)

---

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

(generic-api-key)

---

80-80: 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 (17)

dockerfiles/plugins.txt (17)

3-3: Plugin Version Update: apache-httpcomponents-client-4-api
The version has been updated to 4.5.14-269.vfa_2321039a_83. Verify that this change is compatible with other Jenkins components and that no regression issues have been reported with this version.

🧰 Tools

🪛 Gitleaks (8.21.2)

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

(generic-api-key)

---

9-9: Plugin Version Bump: checks-api
The version is updated to 2.2.2. Ensure this minor update aligns with any dependency requirements and review the changelog for potential backward‑incompatible fixes.

---

13-13: Plugin Version Update: configuration-as-code
The version is now 1932.v75cb_b_f1b_698d. Please verify that this update has been tested against your configuration pipelines to avoid any unexpected behavior.

---

15-15: Plugin Version Bump: credentials
This update to version 1408.va_622a_b_f5b_1b_1 may include important security patches or fixes. Confirm with the release notes that no breaking changes affect systems relying on credential handling.

---

36-36: Plugin Version Update: junit
The junit plugin version has been updated to 1314.vd966e9a_88895. Double-check that this version is fully compatible with your testing frameworks and does not introduce any discrepancies in test reporting.

---

45-45: Plugin Version Update: pipeline-build-step
The plugin now uses version 555.v589d5c24a_3d6. Verify that this change does not disrupt existing pipeline build tasks and is validated in your pipeline tests.

---

47-47: Plugin Version Update: pipeline-graph-view
Upgraded to 409.v98f212e980b_4, ensure that any UI components or dependencies on this plugin are checked for compatibility in your Jenkins environment.

---

48-48: Plugin Version Update: pipeline-groovy-lib
The new version is 752.vdddedf804e72. It’s advisable to verify that updates in the Groovy library do not affect pipeline script executions or Groovy compatibility.

---

54-54: Plugin Version Bump: pipeline-rest-api
The version has been bumped to 2.35. Please ensure that all REST API endpoints used in your jobs or integrations are functioning as expected after this update.

---

57-57: Plugin Version Update: pipeline-stage-view
Updated to version 2.35. It is recommended to validate that this change does not adversely impact the visualization of pipeline stages in Jenkins.

---

65-65: Plugin Version Update: ssh-slaves
The update to 3.1031.v72c6b_883b_869 should be reviewed for any connectivity or compatibility improvements. Checking the changelog for SSH-related fixes is advised.

---

66-66: Plugin Version Update: sshd
The new version 3.350.v1080103a_10fd should be assessed to ensure that security configurations remain intact and that there are no adverse impacts on slave node communications.

---

69-69: Plugin Version Update: token-macro
Token-macro has been updated to 444.v52de7e9c573d. Make sure this update does not affect macro expansions in your pipeline or job configurations.

---

75-75: Plugin Version Update: workflow-cps
The workflow-cps plugin now uses version 4018.vf02e01888da_f. Confirm that this update integrates seamlessly with your pipeline scripts and does not introduce unexpected behavior in CPS transformation.

---

77-77: Plugin Version Bump: workflow-job
Updated to version 1505.vea_4b_20a_4a_495, this change should be cross-checked with any updates in job configuration syntax or stability improvements outlined in the release notes.

---

81-81: Plugin Version Update: workflow-support
The update to 946.v2a_79d8a_4b_e14 may bring performance improvements or bug fixes. Please validate that this version meets your support and stability requirements in production pipelines.

---

1-83: Note on Static Analysis Warnings (Generic API Keys)
Multiple static analysis warnings flagged generic API key detections on various lines. These appear to be false positives triggered by the structure of the plugin version strings. It is recommended to verify and, if necessary, configure false-positive suppression rules to avoid confusion.

🧰 Tools

🪛 Gitleaks (8.21.2)

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

44-44: 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)

---

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

(generic-api-key)

---

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

(generic-api-key)

---

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.