Hello Jesse, thanks for your answer. That sounds reasonable enough to me, we were actually certain there was a reason why Jenkins would not call those post action for an aborted build. You just confirmed our thoughts, we will re work our jobs i they are not able to "properly" abort. Thanks again, Anthony
On Fri, Jul 26, 2013 at 2:38 PM, Jesse Glick <[email protected]> wrote: > On Fri, Jul 26, 2013 at 2:27 PM, Anthony Dahanne > <[email protected]> wrote: > > When I interrupt an executor, using : > > > > executor.interrupt(Result.ABORTED); > > This seems correct: you are aborting the build. > > > the post steps, and post actions will NOT get executed. > > Which seems right. > > > I still want those post actions to be executed, to clean the workspace & > all > > If workspaces need cleaning, that should be done when a build starts, > not when it ends. Whatever the case may be, this seems orthogonal to > your plugin: Jenkins should behave reasonably when someone e.g. clicks > the red X on a running build. > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
