On Thursday, 2 May 2013, JonathanRRogers wrote: > On Thursday, May 2, 2013 2:50:44 PM UTC-4, LesMikesell wrote: >> >> On Thu, May 2, 2013 at 1:26 PM, Kevin Fleming (BLOOMBERG/ 731 LEXIN) >> <[email protected]> wrote: >> > This change would not have been in the Jenkins changelog, because it >> wasn't >> > technically a Jenkins change. It's a change in the SSH Slaves plugin. >> >> Shouldn't something note when the things distributed with the core >> package change in ways that affect behavior? Or are all users >> supposed to know the internal workflow across all the plugins? >> >> > I'm glad I came across this thread while I'm still on version 0.22. I'll > make sure not to upgrade to a version which breaks things so fundamentally. >
0.23 and 0.24 have a race condition where there is a 10-15% chance that you will loose your credentials after rebooting the first time post installation. 0.25 should be fine. This is mostly a UI change, thought the consolidation makes life easier when you need to change credentials in bulk for slaves. A similar change will be coming down the line for, eg subversion, git, etc (the blocker for now being getting a consistent credential type for the many auth mechanisms for the scm systems) > -- > 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 [email protected] <javascript:_e({}, > 'cvml', 'jenkinsci-users%[email protected]');>. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- Sent from my phone -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
