[JIRA] (JENKINS-56387) Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild()

[m...@thomaskeller.biz (JIRA)]

Title: Message Title

Thomas Keller commented on JENKINS-56387   Re: Upgrading to 2.150.3 results in No signature of method: org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter.executePostBuild() The pipeline model definition plugin changed this method in v1.3.5, so when you update to this (or a later) version of the plugin while having a pipeline build in-flight, this single build will fail once it is resumed when Jenkins was restarted after the update was installed. Subsequent builds will then run on the new plugin code only and succeed. I understand as well that this is suboptimal (and I wonder if the whole "serialize builds" thing doesn't add more complexity and corner cases to Jenkins than it does good things), but at least the issue is not permanent. Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.