chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Updated plugin versions for matrix-project and scm-api to their latest releases.

[coderabbitai]

Walkthrough

The pull request involves updating plugin versions in the dockerfiles/plugins.txt file. Specifically, two plugins have been updated: matrix-project and scm-api. The changes are version increments, with matrix-project moving from version 840.v812f627cb_578 to 845.vffd7fa_f27555, and scm-api updating from 698.v8e3b_c788f0a_6 to 703.v72ff4b_259600. No other plugins were added or removed.

Changes

File	Change Summary
dockerfiles/plugins.txt	Updated plugin versions: - matrix-project: 840.v812f627cb_578 → 845.vffd7fa_f27555 - scm-api: 698.v8e3b_c788f0a_6 → 703.v72ff4b_259600

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #310: Updates versions of plugins in dockerfiles/plugins.txt
• chore(jenkins): Updates Jenkins plugins #320: Modifies a plugin version in dockerfiles/plugins.txt
• chore(jenkins): Updates Jenkins plugins #331: Updates a plugin version in dockerfiles/plugins.txt

Suggested labels

repo

Poem

🐰 Plugins hopping, versions light,
Updating bits with coding might,
Matrix and SCM take their leap,
A version dance, so clean and neat!
Dockerfiles sing their version song 🚀

---

📜 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 2889322 and a77099f.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (2 hunks)

🧰 Additional context used

🪛 Gitleaks (8.21.2)

dockerfiles/plugins.txt

61-61: 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 (3)

dockerfiles/plugins.txt (3)

Line range hint 40-61: Test these plugin updates in a staging environment.

Since these updates involve core plugins (matrix-project and scm-api), it's recommended to:

1. Test these changes in a staging environment first
2. Verify that existing jobs using matrix configurations continue to work
3. Check the Jenkins system logs after upgrade for any compatibility warnings

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

---

40-40: Verify compatibility with dependent plugins.

The matrix-project plugin update from 840.v812f627cb_578 to 845.vffd7fa_f27555 appears to be a minor version increment. However, it's important to verify compatibility with plugins that depend on it.

Run this script to check the changelog and dependencies:

✅ Verification successful

Minor version update appears safe to proceed.

The update from 840.v812f627cb_578 to 845.vffd7fa_f27555 represents a minor version increment with no indication of breaking changes. The version format follows Jenkins' standard versioning scheme, and the small version jump (840 to 845) suggests minimal risk.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check changelog and dependencies for matrix-project plugin

# Get plugin info and dependencies
curl -s "https://updates.jenkins.io/download/plugins/matrix-project/845.vffd7fa_f27555/matrix-project.hpi.json" | jq '.dependencies'

# Get changelog
curl -s "https://raw.githubusercontent.com/jenkinsci/matrix-project-plugin/master/CHANGELOG.md"

Length of output: 5247

---

61-61: Verify compatibility with dependent plugins.

The scm-api plugin update from 698.v8e3b_c788f0a_6 to 703.v72ff4b_259600 appears to be a minor version increment. However, since this is a core API plugin used by many other plugins (like git, github, etc.), it's crucial to verify compatibility.

Run this script to check the changelog and dependencies:

✅ Verification successful

Update appears safe to proceed

The version update from 698 to 703 is a consecutive release with no skipped versions. The presence of git and GitHub plugins confirms this is indeed a critical API, but the minimal version increment suggests this is a routine update with low risk.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check changelog and dependencies for scm-api plugin

# Get plugin info and dependencies
curl -s "https://updates.jenkins.io/download/plugins/scm-api/703.v72ff4b_259600/scm-api.hpi.json" | jq '.dependencies'

# Get changelog
curl -s "https://raw.githubusercontent.com/jenkinsci/scm-api-plugin/master/CHANGELOG.md"

# Find plugins that depend on scm-api
rg -l "scm-api:" dockerfiles/

Length of output: 12088

---

Script:

#!/bin/bash
# Get recent releases and check for dependent plugins
# Get latest releases from GitHub
gh api repos/jenkinsci/scm-api-plugin/releases --paginate | jq -r '.[].name' | head -n 5

# Check for dependent plugins in plugins.txt
echo "Plugins depending on scm-api:"
grep -B1 -A1 "scm-api:" dockerfiles/plugins.txt

# Check if there are any git or github related plugins
echo -e "\nRelated SCM plugins:"
grep -E "git|github|bitbucket|gitlab|mercurial|svn" dockerfiles/plugins.txt

Length of output: 646

🧰 Tools

🪛 Gitleaks (8.21.2)

61-61: 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.