You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
We routinely run into problems where we want to use the Helm charts to update Jenkins, but the configuration for plugins contains conflicts and we need to debug it on the fly. For example, our latest update attempt yielded errors like this:
Plugin git:5.7.0 depends on credentials:1405.vb_cda_74a_f8974, but there is an older version defined on the top level - credentials:1393.v6017143c1763,
I'm not sure if I missed this feature and it already exists, but it would be nice if we could specify that we want to install a certain minimum version -- e.g. credentials no less than 1393.v6017143c1763, but allow the deployment to install the required version needed for other plugins to run.
Describe the solution you'd like
Maybe something like credentials:>=1393.v6017143c1763 or credentials:^1393.v6017143c1763.
Describe alternatives you've considered
In the meantime I've removed credentials from our config so it uses whichever is suitable for the plugins depending on it.
Additional context
I've inherited this process/system with little documentation to work from, so I am also open to advice on why this should not be a feature and what I should be doing instead. :)
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe
We routinely run into problems where we want to use the Helm charts to update Jenkins, but the configuration for plugins contains conflicts and we need to debug it on the fly. For example, our latest update attempt yielded errors like this:
I'm not sure if I missed this feature and it already exists, but it would be nice if we could specify that we want to install a certain minimum version -- e.g.
credentials
no less than1393.v6017143c1763
, but allow the deployment to install the required version needed for other plugins to run.Describe the solution you'd like
Maybe something like
credentials:>=1393.v6017143c1763
orcredentials:^1393.v6017143c1763
.Describe alternatives you've considered
In the meantime I've removed
credentials
from our config so it uses whichever is suitable for the plugins depending on it.Additional context
I've inherited this process/system with little documentation to work from, so I am also open to advice on why this should not be a feature and what I should be doing instead. :)
The text was updated successfully, but these errors were encountered: