https://issues.jenkins-ci.org/browse/JENKINS-18608
Looks like we need to fix this soon to reduce the damage.
On 08/07/2013 10:35 AM, Stephen Connolly wrote:
Yeah Jenkins core is not smart enough to stop when it can't install the
dependent plugins.
Hopefully all should be good once you get all three updated.
You could update the JIRA for me as I am on a smartphone for the rest of today!
On Wednesday, 7 August 2013, Larry Shatzer, Jr. wrote:
I guess some of them were only in the update center, since I just found
another after I forced it to check for new updates. It's restarting now.
On Wed, Aug 7, 2013 at 11:30 AM, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
Did you ensure upgrading *all* three or just "some" of them.
If you go ssh credentials 1.0 or ssh slaves 1.0 you *must* do both
On Wednesday, 7 August 2013, Larry Shatzer, Jr. wrote:
And someone just reported the same stacktrace on the users list
with
this ticket: JENKINS-19104
On Wed, Aug 7, 2013 at 11:22 AM, Larry Shatzer, Jr.
<lar...@gmail.com> wrote:
I'm now seeing this when it tries to connect to a SSH slave:
http://pastebin.com/F5e9rTVX
Also my windows slaves (setup as windows services via DCOM),
are
hanging on checking java version.
I've now switched the critical slaves to be JNLP slaves, just
to
get it back up and working.
On Wed, Aug 7, 2013 at 5:54 AM, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
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 Developers" group.
To unsubscribe from this group and stop receiving emails
from it, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com.
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 "Jenk
--
Sent from my phone
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Jenkins Enterprise, our professional version of Jenkins
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
