chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Updated multiple Jenkins plugin versions, including:
    • Matrix Auth
    • Mina SSHD API
    • Pipeline Build Step
    • Pipeline Model plugins
    • Workflow-related plugins

These updates include minor version increments across various Jenkins ecosystem plugins, potentially improving stability and introducing minor bug fixes.

[coderabbitai]

Walkthrough

This pull request updates multiple Jenkins plugin versions in the dockerfiles/plugins.txt file. The changes involve incrementing versions for various plugins across different categories, including workflow, pipeline, authentication, and SSH-related plugins. The updates range from minor version bumps to slightly more significant version changes, suggesting maintenance and potential bug fixes or compatibility improvements.

Changes

File	Changes
dockerfiles/plugins.txt	Updated versions for multiple plugins including: - matrix-auth: 3.2.3 → 3.2.4 - mina-sshd-api plugins: 2.14.0-138 → 2.14.0-143 - pipeline-* plugins: 2.2218 → 2.2221 - workflow-* plugins: Various incremental updates

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #265: Updates the version of plugins in dockerfiles/plugins.txt
• chore(jenkins): Updates Jenkins plugins #276: Includes updates to the workflow-cps plugin version
• chore(jenkins): Updates Jenkins plugins #277: Updates the matrix-auth, mina-sshd-api-common, and mina-sshd-api-core plugins

Suggested labels

repo

Poem

🐰 Plugins dancing, versions bright,
Updating Jenkins with all my might,
From workflow to pipeline's gleam,
Each number change, a rabbit's dream!
Hop, hop, update with delight! 🚀

---

📜 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 80ab2a5 and 6d2381a.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (2 hunks)

🧰 Additional context used

🪛 Gitleaks (8.21.2)

dockerfiles/plugins.txt

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)

---

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 (1)

• GitHub Check: Codacy Security Scan

🔇 Additional comments (5)

dockerfiles/plugins.txt (5)

42-43: LGTM! SSH API updates look safe.

The updates to mina-sshd-api plugins are using standard Jenkins plugin version format. The static analysis warnings about API keys can be safely ignored as these are legitimate Jenkins plugin version strings.

🧰 Tools

🪛 Gitleaks (8.21.2)

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)

---

Line range hint 1-83: Overall LGTM with recommendations.

The plugin updates look consistent and follow standard Jenkins plugin versioning patterns. However, before merging:

1. Ensure these updates are tested in a staging environment
2. Plan for a maintenance window as these updates touch core Jenkins components (security, pipeline, workflow)
3. Have a rollback plan ready, especially for the security-related updates

🧰 Tools

🪛 Gitleaks (8.21.2)

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)

---

73-76: Verify workflow plugins are on latest stable versions.

Multiple workflow plugins have been updated. Let's verify these are the latest stable versions and check for any breaking changes.

Also applies to: 78-78, 80-80

---

39-39: Verify security implications of matrix-auth update.

The update to matrix-auth plugin (3.2.3 → 3.2.4) is a minor version bump. Let's verify if this update includes any security fixes.

✅ Verification successful

No security implications in matrix-auth update

The update from 3.2.3 to 3.2.4 contains only infrastructure modernization changes (Java EE 9 APIs support) and dependency updates. No security fixes are included in this release.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for security advisories and changelog for matrix-auth plugin
curl -s "https://plugins.jenkins.io/matrix-auth/releases/" | grep -A 5 "3.2.4"

Length of output: 65643

---

Script:

#!/bin/bash
# Get release information from GitHub API
curl -s "https://api.github.com/repos/jenkinsci/matrix-auth-plugin/releases/tags/matrix-auth-3.2.4" | jq -r '.body'

Length of output: 618

---

45-45: Verify pipeline plugins compatibility.

All pipeline plugins have been updated to consistent versions (2.2221.vc657003fb_d93). Let's verify compatibility with the updated workflow plugins.

Also applies to: 51-53, 56-56

✅ Verification successful

Pipeline plugins are properly aligned and compatible

All pipeline model plugins are at consistent version 2.2221.vc657003fb_d93 and workflow plugins are at compatible versions. No version conflicts detected.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for known compatibility issues between pipeline and workflow plugins
curl -s "https://plugins.jenkins.io/pipeline-model-definition/releases/" | grep -A 10 "2.2221"

# Check if these versions are marked as compatible in the Jenkins Plugin Site
curl -s "https://plugins.jenkins.io/pipeline-model-definition/" | grep -A 5 "Dependencies"

Length of output: 65748

---

Script:

#!/bin/bash
# List all pipeline-related plugins and their versions
echo "=== Pipeline Plugin Versions ==="
grep -i "pipeline" dockerfiles/plugins.txt

# Check for any workflow plugins that might have dependencies
echo -e "\n=== Workflow Plugin Versions ==="
grep -i "workflow" dockerfiles/plugins.txt

# Look for build step plugin version for compatibility
echo -e "\n=== Build Step Plugin Version ==="
grep "pipeline-build-step" dockerfiles/plugins.txt

Length of output: 1313

---

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.