On Sat, Feb 28, 2015 at 5:52 PM, Jason Pyeron <[email protected]> wrote:
> > -----Original Message----- > > From: Vincent Latombe > > Sent: Saturday, February 28, 2015 14:48 > > > > Hi, > > > > A good habit is to check the release notes before updating. > > > > on https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin > > Yes, lesson learned. > > I assumed a point release was fine, and that it had been tested in some > sort of CI system. > Jason, I'm grateful that you reported the same problem that I encountered this morning. As far as I've experienced, this was a very rare instance where a minor release of a plugin had a major impact. We're still not as mature with upgrade testing as I'd like (or at least, I'm not as mature with upgrade testing). When I have an upgrade concern, I typically need to construct various upgrade scenarios to work through their functionality. It becomes even more challenging when interacting with the update center, since it is a remote system running "in production". Thanks for noting the problem to the mailing list for the rest of us who learned from your observations. Mark Waite -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFuG9t_F4zL%3D7ncg53XdZG9dZD-GdWQ1dtTN53DrKjm8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
