I’m currently implementing a better pipeline support for the static analysis plug-ins (see [1]). >From the documentation of Step it is not clear to me, when to implement a Step >or when to use a method on a returned object. So basically, is a procedural or >object oriented approach desired?
E.g, 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? Or should e.g. step 1 (parse warnings) return an object that has some methods, e.g. to copy the files (2) to the build folder? When I implement everything as Step then the list of available steps will grow very fast (name clashes will be also very probable) Are there some recommendations or is this decision up to the plugin author? [1] https://wiki.jenkins.io/display/JENKINS/Static+Analysis+in+Pipelines -- 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/9E4A672A-2BE5-4352-AFF2-0298751EA7CE%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP
