As part of my improvements to the Credentials plugin I am pushing a whole new set of releases of these plugins.
Credentials 1.6 is backwards compatible with all previous releases. It should be safe to upgrade that one on its own. SSH Credentials 1.0 requires Credentials 1.6 and includes a change to the on-disk data format. The consequence of this is that if you upgrade to SSH Credentials 1.0 you may loose credentials if you subsequently decide you made a mistake and decide to revert back to an earlier version... this is because the SSHUserPassword credentials have been migrated to the new StandardUsernamePasswordCredentials type in Credentials 1.6. This plugin is a new Major Version due to the deprecation of quite a few methods and classes. Note that if you do not upgrade SSH Slaves to a release that uses the new method signatures you may find that the Username/password credentials cannot be located. SSH Agent 1.2 requires SSH Credentials 1.0 and Credentials 1.6 but has no other impact. SSH Slaves 1.0 requires SSH Credentials 1.0 and Credentials 1.6. Given that this plugin is widely used, it advertises a change to the on-disk data format (despite there technically not being any) to prevent people accidentally upgrading without being aware that there is a potential impact (namely the changes in SSH Credentials 1.0) This version gets a new Major Version due to the major version change of SSH Credentials. I have done quite a bit of testing, and I am quite confident that the changes are safe... *but* you need to jump with all of them in one go, in other words IF you upgrade either of SSH Slaves or SSH Credentials to 1.0 you MUST ENSURE the other is upgraded also. Thanks for listening -Stephen -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
