On Mon, Jul 24, 2017 at 4:55 PM, Ullrich Hafner <[email protected]> wrote: > in a freestyle project the warnings publisher does the following things > (among others): > 1) parse files for warnings > 2) copy files to build folder for future reference > 3) compute difference (new, old, fixed warnings) with regard to a reference > build > 4) blame authors of warnings > 5) publish warnings as persistent Action > > So my question is: is everything a step?
With the possible exception of #4, all of these sound like they should be part of a single `Step`. (Or if the freestyle version can reasonably be factored into a `SimpleBuildStep`, there is no need for a `workflow-step-api` dependency at all.) Compare `JUnitResultArchiver`. If you do need to break functionality apart in order to offer greater flexibility, just provide multiple steps. OO style is not well supported. -- 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/CANfRfr36XfAy%2BBwgJMP3fwSntyCx425aTnrzMmFPtJ5e3zXPdg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
