chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Upgraded key system components to newer versions, ensuring improved compatibility, stability, and performance.

[coderabbitai]

Walkthrough

This pull request updates version numbers for several plugins in the dockerfiles/plugins.txt file. The updates include incremented versions for apache-httpcomponents-client-4-api, junit, pipeline-build-step, pipeline-groovy-lib, workflow-cps, and workflow-job. These changes modify only the version declarations and do not introduce any new features or modify the overall control flow.

Changes

File

Change Summary

dockerfiles/plugins.txt

Updated plugin versions: - apache-httpcomponents-client-4-api: 4.5.14-208.v438351942757 → 4.5.14-269.vfa_2321039a_83 - junit: 1312.v1a_235a_b_94a_31 → 1314.vd966e9a_88895 - pipeline-build-step: 551.v178956c49ef8 → 555.v589d5c24a_3d6 - pipeline-groovy-lib: 751.v709f84f7d768 → 752.vdddedf804e72 - workflow-cps: 4014.vcd7dc51d8b_30 → 4018.vf02e01888da_f - workflow-job: 1498.v33a_0c6f3a_4b_4 → 1505.vea_4b_20a_4a_495

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #306: Updates version numbers in dockerfiles/plugins.txt, providing a direct match to the modifications in this PR.
• chore(jenkins): Updates Jenkins plugins #296: Focuses on a version bump for the junit plugin, aligning closely with the changes here.
• chore(jenkins): Updates Jenkins plugins #277: Implements multiple plugin version updates in the same file, mirroring the modifications in this PR.

Suggested labels

repo

Poem

In fields of code I dash and hop,
Updating plugins, I never stop.
Each version leap with a joyful beat,
A burrow of fixes, oh-so-sweet.
Hoppy commits make my heart go tick,
Code and carrots — a perfect click!

---

📜 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 e2bac9b and 42af30e.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (4 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)

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

• GitHub Check: Codacy Security Scan

🔇 Additional comments (7)

dockerfiles/plugins.txt (7)

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 update is compatible with the dependent plugins and the runtime environment. Also, note that static analysis flagged this line as a potential generic API key—this appears to be a false positive given that it is simply a version string.

🧰 Tools

🪛 Gitleaks (8.21.2)

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

(generic-api-key)

---

36-36: Plugin Version Update: junit
The version for junit has been updated to 1314.vd966e9a_88895. Please ensure that this change is consistent with your testing frameworks and any integrations that might depend on this version.

---

45-45: Plugin Version Update: pipeline-build-step
The version for pipeline-build-step has been updated to 555.v589d5c24a_3d6. Confirm that your pipeline jobs have been tested against this new version to avoid any unforeseen disruptions.

---

48-48: Plugin Version Update: pipeline-groovy-lib
The update to 752.vdddedf804e72 for pipeline-groovy-lib should be verified for compatibility with existing pipeline scripts. Ensure that any changes in the plugin do not break your current groovy-based configurations.

---

75-75: Plugin Version Update: workflow-cps
The workflow-cps plugin has been updated to 4018.vf02e01888da_f. It's advisable to review the release notes for potential breaking changes and run integration tests to confirm stability with your current pipelines.

---

77-77: Plugin Version Update: workflow-job
The version for workflow-job has been updated to 1505.vea_4b_20a_4a_495. Please verify that this version update does not adversely affect job configurations or pipeline behaviors in your Jenkins setup.

---

1-83: Static Analysis Notice: Generic API Key Warning
A static analysis tool flagged a potential generic API key on line 3. This appears to be a false positive due to the pattern in the version string. Nonetheless, please double-check that no sensitive credentials are exposed in this file.

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