chore(jenkins): Updates Jenkins plugins

[gounthar]

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

Summary by CodeRabbit

• Chores
  • Updated pipeline-input-step plugin to a newer version

[coderabbitai]

Walkthrough

This pull request involves a specific update to the Jenkins plugin version for pipeline-input-step in the dockerfiles/plugins.txt file. The plugin version has been upgraded from 495.ve9c153f6067b_ to 508.v584c0e9a_2177, with no other changes made to the file or surrounding context.

Changes

File	Change Summary
dockerfiles/plugins.txt	Updated pipeline-input-step plugin version from 495.ve9c153f6067b_ to 508.v584c0e9a_2177

Possibly related PRs

• chore(jenkins): Updates Jenkins plugins #310: Updates versions of plugins in dockerfiles/plugins.txt

Suggested labels

repo

Poem

🐰 A plugin's version, now refined,
Hopping forward, leaving old behind,
In plugins.txt, a single line
Leaps to progress, clean and kind
Jenkins magic, version redesigned! 🚀

---

📜 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 93741f6 and 7652832.

📒 Files selected for processing (1)

• dockerfiles/plugins.txt (1 hunks)

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

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: Codacy Security Scan

🔇 Additional comments (1)

dockerfiles/plugins.txt (1)

49-49: LGTM! Please verify the version compatibility.

The update of pipeline-input-step from 495.ve9c153f6067b_ to 508.v584c0e9a_2177 looks good. However, let's verify:

Run this script to check the latest version information and compatibility:

✅ Verification successful

Version update verified successfully

The update to 508.v584c0e9a_2177 is correct as it's the latest stable release (Jan 2025). The changes include performance improvements and security updates, with no breaking changes reported.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the pipeline-input-step plugin version and its compatibility

# Get the latest version info from Jenkins update center
curl -s https://updates.jenkins.io/current/update-center.actual.json | jq '.plugins."pipeline-input-step"' 

# Check if there are any known compatibility issues
curl -s https://updates.jenkins.io/current/update-center.actual.json | \
  jq '.plugins."pipeline-input-step".dependencies[] | select(.optional==false)' 

# Look for any upgrade warnings in the changelog
curl -s https://raw.githubusercontent.com/jenkinsci/pipeline-input-step-plugin/master/CHANGELOG.md || \
  echo "Changelog not accessible"

Length of output: 4717

---

Script:

#!/bin/bash
# Get the latest release information from GitHub API
curl -s -H "Accept: application/vnd.github.v3+json" \
     "https://api.github.com/repos/jenkinsci/pipeline-input-step-plugin/releases/latest"

# List recent releases to check for any breaking changes
curl -s -H "Accept: application/vnd.github.v3+json" \
     "https://api.github.com/repos/jenkinsci/pipeline-input-step-plugin/releases?per_page=5"

# Check if the specific version exists in tags
curl -s -H "Accept: application/vnd.github.v3+json" \
     "https://api.github.com/repos/jenkinsci/pipeline-input-step-plugin/tags" | \
     grep -i "508.v584c0e9a_2177" || echo "Version not found in tags"

Length of output: 17264

---

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.