LDAP plugin, warning after Jenkins upgrade v1.638

[Lavr L]

Hi

I upgraded Jenkins to last release 1.638 and now I have the following warning for LDAP plugin:

Warning: the new version of this plugin claims to use a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details.

Ldap works ok for my Jenkins. 

Where to find these release notes that was mentioned in warning and should I downgrade if LDAP works for me?what the impact expected after plugin downgrade?

Thanks in advance for support and ideas,

Best regards, 

Lavr

[Daniel Beck]

Click the plugin name and then scroll down.

> --
> You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3187dc1f-74e7-4717-951e-4a81cc521b92%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Stephen Connolly]

In case you are having difficulty the change in question was:

Turned the group membership lookup into a strategy.

That changed the configuration format of the LDAP security realm. This is normally not a big deal... as long as you do not roll back the plugin... if you roll the plugin back to version 1.9 or earlier, then those versions will no longer be able to read the new configuration format and you may get locked out.

All Jenkins plugins can set a flag: compatibleSinceVersion

If set, then you get the standard boilerplate warning text if you are upgrading from an older version of the plugin than the `compatibleSinceVersion`

Plugin authors are supposed to set this version to the oldest version of the plugin that you can revert to without breaking the ability to parse the data on disk using the older plugin's parser.

Because the message has to be generic, it is typically more scary than it needs to be, but we only have one flag and a speed-bump is better than just having people upgrade unthinkingly, find a bug, revert the plugin to the old version and *BOOM* you are locked out of Jenkins because after the upgrade your configuration was updated to the new format and the downgraded plugin cannot read the new format.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/028ADE0C-D4D7-4FD9-B7D7-DCFD1C451188%40beckweb.net.