I just ran into that....when I did the upgrade and updated all plugins, the Jenkins SSH Slaves plugin was still at v0.27. You must upgrade it to version 1.0. I had to force the update check for it to see it.
On Wed, Aug 7, 2013 at 11:21 AM, Jared Griffith <[email protected]>wrote: > Hopefully I can get a quicker response from the group. I just upgraded > Jenkins to the latest version 1.526 and now my slave nodes won't start at > all. I created a ticket for it, but have yet to get a response. Trying to > downgrade the application has not resolved the issue. I'm at a loss since > I need all of my nodes to be working properly. > Here's the ticket I created: > https://issues.jenkins-ci.org/browse/JENKINS-19104 > > -- > > Jared Griffith > Linux Administrator, PICS Auditing, LLC > P: (949) 936-4574 > C: (909) 653-7814 > > <http://www.picsauditing.com> > > 17701 Cowan #140 | Irvine, CA | 92614 > > Join PICS on LinkedIn and Twitter! > > <https://twitter.com/PICSAuditingLLC> > > -- > 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. > > > -- Jeff Vincent See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent -- 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.
