-- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is copyright PD Inc, subject to license 20080407P00.
> -----Original Message----- > From: jenkinsci-users@googlegroups.com > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Daniel Beck > Sent: Saturday, February 28, 2015 17:23 > To: jenkinsci-users@googlegroups.com > Subject: Re: Borked my jenkins doing a plugin update > > > On 28.02.2015, at 19:11, Jason Pyeron <jpye...@pdinc.us> wrote: > > > Anyone up for a post mortem? > > Caused by the fix to SECURITY-125: > https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+ Advisory+2015-02-27 > > So it should be an unusual enough situation. Additionally, > facilities to prevent this problem in the future were added > to update center generation code and Jenkins itself. > > > I shall never again assume the safety of plugin updates... > > Checking changelogs of software before you're updating is a > reasonable safeguard against getting surprised by undesirable > changes in general. I say with tongue in cheek, "click link, scroll and read 'Version 1.4.1 (Feb 27, 2015) Bundled in 1.596.1 and 1.600. Do not update to this release; it will be removed from the update center (INFRA-250). If you have already updated, use Plugin Manager > Installed to revert to your previous version.`" -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5DCDC8555A664C1CAD9F00744B6E6542%40black. For more options, visit https://groups.google.com/d/optout.
