Thanks Jesse, With hindsight, an obvious solution. :)
I think the simple build step wouldn't help, as I would then have to ensure that it was run first, thereby reintroducing the specific run order. Thanks again On Tuesday, 11 September 2018 16:44:12 UTC+1, Jesse Glick wrote: > > On Tue, Sep 11, 2018 at 9:01 AM steadyonabix <[email protected] > <javascript:>> wrote: > > This plugin currently uses the prebuild() method to configure and start > a standalone Java application, the OWASPZAP scanner. > > Probably this should simply be folded into your `SimpleBuildStep.perform`. > > (If you really need to have something that runs before and after the > build as a whole for some reason, you can create a > `[Simple]BuildWrapper`. But I cannot see how that would be the case > here.) > > > I watched the Youtube video on refactoring for pipeline and it > highlighted the need to avoid using prebuild() as it presupposes a specific > run order. > > Noted in: https://javadoc.jenkins.io/jenkins/tasks/SimpleBuildStep.html > -- 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/fff4bab4-967a-438c-b097-956e0e26148e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
