it's now (hopefully) marked as incompatible - (thanks for the pointer - got there before the release was deployed!)
As it's not just a simple reconfig the announcement was still needed. On Tuesday, 8 April 2014 20:57:09 UTC+1, Daniel Beck wrote: > > Shouldn't this info be distributed using update center metadata? > > E.g.: > > https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions > > > On 08.04.2014, at 21:52, teilo <[email protected] <javascript:>> wrote: > > > Hi, > > > > Buildflow 0.11 is in the process of releasing and should hit the update > center in a few hours. > > > > This version contains a significant intentional change that may affect > you if you using functionality that was unintentionally exposed. > > > > The Flow is now a flyweight task and as such has no workspace associated > with it and will execute on the master. > > > > If you are relying on this functionality then you should not upgrade > without migrating the functionality you need to another job. > > > > /James > > > > > > -- > > 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] <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > > -- 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/d/optout.
