On Thursday, 2 May 2013, Haszlakiewicz, Eric wrote: > eh? I now need to manage my credentials within Jenkins, instead of just > the contents of my .ssh directory?
If you have all they keys Jenkins needs in your .ssh directory then this makes your life easier... You just tell it to use those credentials. If you don't then this makes your life easier. It is a great pity that nobody tested 0.23 (or the -SNAPSHOT with the credentials change available since jan.) With greater testing the race condition that can cause migrated credentials to get lost would have been caught and fixed. As soon as I spotted the issue, I fixed it and cut the 0.25 release. Well that's a pretty huge change, and I didn't see any mention of it in the > main changelog. :( I guess I'll take a look and see what I need to configure there. Shouldn't have to configure anything if you go 0.22->0.25 It just makes it easier to share credential config across build slaves and also use those credentials for other ssh related build steps > Thanks for the pointer. > > Eric > > > -----Original Message----- > > From: jenkinsci-users@googlegroups.com <javascript:;> > > [mailto:jenkinsci-<javascript:;> > > us...@googlegroups.com <javascript:;>] On Behalf Of CHAVANNE Robert > > Sent: Thursday, May 02, 2013 10:43 AM > > To: jenkinsci-users@googlegroups.com <javascript:;> > > Subject: Re: can't start slaves anymore, ssh auth failing > > > > Hello Eric, > > We had the same kind of problem. > > I think you should take a look at "manage Credentials" in manage Jenkins. > > We had to create credential to fix the issue. > > I hope it can help. > > > > Regards, > > Robert > > > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
