I can provide whatever is needed. Would a stripped down version of the plugin with just the absolute minimal amount of code needed to replicate the issue be what is needed? And where should I provide this? I can put it on a new public GitHub repo?
On Monday, April 2, 2018 at 8:27:58 PM UTC+3, Jesse Glick wrote: > > On Mon, Apr 2, 2018 at 12:07 PM, Daniel Anechitoaie > <[email protected] <javascript:>> wrote: > > If I run my plugin just on master (so not inside a > > MasterToSlaveCallable) it does get interrupted ok (not instantly but as > soon > > as zip operation is finished and without errors). > > So my understanding is that maybe something in how > MasterToSlaveCallables > > are handled cause this strange behaviour since on master and on > pipelines > > works ok and the problem > > seems to be just for MasterToSlaveCallables. > > Not sure offhand. Sounds like it could be a bug in Jenkins core. Would > need to have a minimal self-contained test case that could be run > through a debugger to track down the culprit. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6f08246a-d3c1-4e08-9860-c7c85b548e19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
