Using jenkins-plugins with a constraint of a specific jenkins version

[Jitrixis]

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us what version of Renovate you run.

37

If you're self-hosting Renovate, select which platform you are using.

gitlab.com

What is your question?

Hello,

I'm using renovate to update a file jenkins-plugins.txt but it update all plugins to the latest version and some are not compatible with the latests docker version of Jenkins. So there are not compatible. Is there a way to specify the jenkins version as a depency constraint ?

Logs (if relevant)

Logs

Copy/paste the relevant log(s) here, between the starting and ending backticks

[rarkins]

Not currently supported. It would be necessary to add "jenkins version" awareness to the plugins datasource here: https://github.com/renovatebot/renovate/blob/main/lib/modules/datasource/jenkins-plugins/index.ts

Can you create a reproduction repo for this? Instructions to follow

[rarkins]

It must be a match of the constraint. If your constraint is an exact version then you must match the exact version. Try using a range constraint instead of exact version

[anna-agafonova]

ah, that makes sense, thanks. will test.

[rarkins]

We probably should also make changes to the constraints we detect automatically if the intention of them is "or greater"

[anna-agafonova]

I have version range defined like this:

  "constraintsFiltering": "strict",
  "constraints": {"jenkins": ">= 2.0 <= 2.414.3"},

This results in constraints not being applied at all, e.g. ansible plugin getting updated by renovate to 307.va_1f3ef06575a_, which requires Jenkins 2.426.2.

[rarkins]

A reproduction is needed for any deeper help, I can't locate one anywhere above

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.

To get started, please read our guide on creating a minimal reproduction.

We may close the discussion if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.

Good luck,

The Renovate team

[jan-kantert]

I can confirm the issue. We experience exactly the same thing.

[rarkins]

Reproduction needed

[simonhaenisch]

I believe this has been solved by #26155?

[anna-agafonova]

reduced. plugins list contains multiple plugins, because these are the dependencies of the offending mailer plugin in this example.
also run renovate 37.246.2 on the repository: anna-agafonova/minimal-reproduction-renovate#3

[rarkins]

The problem only occurs when grouping?

[anna-agafonova]

okay, removed the grouping parameters, they are not related.

[anna-agafonova]

any update? is the minimal reproduction acceptable?

[rarkins]

Is your config minimal? i.e. delete any part of it and the problem goes away?

[bsloan-icl]

We're experiencing the exact same issue @anna-agafonova has created in their repo. Even with a minimal configuration, it ignores the constraints that have been set.

[rarkins]

The versioning in use is maven, and <= is not valid syntax for maven versioning. I tried switching to semver-coerced here: https://github.com/renovate-reproductions/26151/blob/main/renovate.json

The result is this:

DEBUG: Filtered 4 releases for dark-theme due to constraintsFiltering=strict: 453.v3f988b_c80202, 460.va_de13e406a_14, 465.vd8b_419b_0728f, 479.v661b_1b_911c01 (repository=renovate-reproductions/26151)
DEBUG: Found no satisfying versions with 'semver-coerced' versioning (repository=renovate-reproductions/26151)

I think this means that the constraints filtering worked ok (4 out of 44 were filtered out) but then semver-coerced regarded the resulting 41 as all invalid, probably due to the a-z characters. loose versioning could handle these but it does not support constraints like <=.

I don't think there's any solution to this without adding something like constraintsVersioning to allow constraints to use different versioning to normal.

[bsloan-icl]

Thanks for looking into this. I guess it's possible with the regex custom manager? But then that sort of defeats the point of having a dedicated jenkins manager.

[rarkins]

I don't think it's possible then either

[bsloan-icl]

If it isn't possible to use constraints filtering (e.g. >= and <=) for the Jenkins manager, can this be converted to an issue? It would be a useful feature to have.

[rarkins]

Converted to feature request: #31831