chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Updated several underlying components to their latest versions to enhance overall stability and performance.

[coderabbitai]

Walkthrough

This update revises multiple plugin versions in the dockerfiles/plugins.txt file. Each plugin version is incremented to a newer value, reflecting maintenance updates. Changes include updates for plugins such as 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, and workflow-support.

Changes

File	Change Summary
dockerfiles/plugins.txt	Updated plugin versions: 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: Updates a broad set of plugin versions in dockerfiles/plugins.txt, directly aligning with the current changes.
• chore(jenkins): Updates Jenkins plugins #304: Involves modifications to multiple plugins (configuration-as-code, credentials, ssh-slaves, workflow-cps) similar to those in this PR.
• chore(jenkins): Updates Jenkins plugins #306: Addresses a wide update of plugin versions in dockerfiles/plugins.txt, showing strong code-level connections with this update.

Suggested labels

repo

Poem

I'm a rabbit with hops so light,
Updating plugins feels just right.
Each version change makes me leap with glee,
In our code burrow, new carrots I see.
With a joyful twitch and a digital cheer,
I celebrate updates that are crystal clear!
🐇✨

---

📜 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 fabbb7e.

📒 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: Updated apache-httpcomponents-client-4-api version.
The version has been updated to "4.5.14-269.vfa_2321039a_83". This update appears standard; please confirm that it aligns with your Jenkins plugin compatibility requirements.

🧰 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: Updated checks-api version.
The checks-api version has been bumped to "2.2.2". Ensure that any dependency on this plugin is validated after the upgrade.

---

13-13: Updated configuration-as-code plugin version.
The configuration-as-code plugin is now at "1932.v75cb_b_f1b_698d". This update seems in line with maintenance updates; please verify its compatibility with your current Jenkins setup.

---

15-15: Updated credentials plugin version.
The credentials plugin version is now "1408.va_622a_b_f5b_1b_1". It is recommended to check that this update does not affect any credential handling workflows.

---

36-36: Updated junit plugin version.
The junit plugin version has been updated to "1314.vd966e9a_88895". This looks like a straightforward version bump; please ensure your build and test processes continue to work as expected.

---

45-45: Updated pipeline-build-step version.
The pipeline-build-step plugin is now at "555.v589d5c24a_3d6". Confirm that this update is compatible with your pipeline configurations.

---

47-47: Updated pipeline-graph-view version.
The version for pipeline-graph-view has been updated to "409.v98f212e980b_4". This change appears correct; please verify its visual impact on your dashboards if applicable.

---

48-48: Updated pipeline-groovy-lib version.
The pipeline-groovy-lib plugin now uses version "752.vdddedf804e72". Double-check that this update maintains compatibility with your pipeline groovy scripts.

---

54-54: Updated pipeline-rest-api version.
The pipeline-rest-api version has been bumped to "2.35". This adjustment should be reviewed for any potential impacts on REST-based integrations in your Jenkins pipelines.

---

57-57: Updated pipeline-stage-view version.
The pipeline-stage-view plugin now uses version "2.35". Everything appears standard; please confirm that the stage visualizations are rendered as expected.

---

65-65: Updated ssh-slaves version.
The ssh-slaves plugin version is now "3.1031.v72c6b_883b_869". Make sure this update does not interrupt any remote node configurations.

---

66-66: Updated sshd version.
The sshd plugin has been updated to "3.350.v1080103a_10fd". Confirm that SSH connectivity and related security settings remain unaffected.

---

69-69: Updated token-macro plugin version.
The token-macro plugin is now updated to "444.v52de7e9c573d". This should be verified to ensure macro expansions are processed correctly.

---

75-75: Updated workflow-cps plugin version.
The workflow-cps plugin version has been updated to "4018.vf02e01888da_f". Please validate that this update does not affect any CPS-related pipeline processing.

---

77-77: Updated workflow-job plugin version.
The workflow-job plugin version has been bumped to "1505.vea_4b_20a_4a_495". Ensure that job scheduling and related functionalities continue to operate smoothly.

---

81-81: Updated workflow-support plugin version.
The workflow-support plugin version is now "946.v2a_79d8a_4b_e14". This update appears standard; consider verifying overall workflow stability post-upgrade.

---

1-83: Overall Plugin Updates Review.
All plugin version updates have been applied consistently across the file. Please ensure that these updates are thoroughly tested in your Jenkins environment for compatibility with your current jobs and configurations. Note: Static analysis tools flagged potential API key patterns on several lines; however, these appear to be false positives since the file only contains plugin names and version numbers.

🧰 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.