Skip to content

Fix dependency updates for Jenkins plugins. #397

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

chrisdecker1201
Copy link

I have noticed that dependent plugins are not being updated. Are you having the same problem?

I have not found a way to change this behaviour with the community jenkins_plugin you are using.

Basically, this calls the jenkins-CLI list-plugins command and filters out each plugin that needs to be updated.

The output will normally look like this:

workflow-cps                       Pipeline: Groovy                            3953.v19f11da_8d2fa_ (3975.v567e2a_1ffa_22)
workflow-durable-task-step         Pipeline: Nodes and Processes               1371.vb_7cec8f3b_95e
workflow-job                       Pipeline: Job                               1436.vfa_244484591f (1459.v6c531091efcd)
workflow-multibranch               Pipeline: Multibranch                       795.ve0cb_1f45ca_9a_
workflow-scm-step                  Pipeline: SCM Step                          427.v4ca_6512e7df1
workflow-step-api                  Pipeline: Step API                          678.v3ee58b_469476
workflow-support                   Pipeline: Supporting APIs                   930.vf51d22b_ce488

Therefore every line that ends with a ")" needs an update.

To not change the current behaviour, the default of jenkins_plugin_update_dependencies is false.

@chrisdecker1201
Copy link
Author

Hi @geerlingguy 😄,

can I improve this solution somehow, so you will integrate this fix 🤔?

❤️ Thank you so much for this role. It helps me a lot in my daily work.

Copy link

This pr has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!

Please read this blog post to see the reasons why I mark issues as stale.

@github-actions github-actions bot added the stale label Mar 16, 2025
@github-actions github-actions bot removed the stale label Mar 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant