1. Well, your points might lead to tedious refactoring of old code and design :) but in short, the removal of the possibility (in the new Project-job model) to check the list of previous builders used is the main issue which led for this.
Since it's not convenient to start looking for which files were created during the builders run. for example if four different builders of my plugin ran and each have created it's result, I'd have to look for each possible result file and parse it - instead of simply "pulling" it from the builder - which is much simpler. 2. I will look into that. I've been thinking on the need to shift for the asyncrhonous due to step length concern mainly. 3. Where can I read the DOC on the advanced API (such as the one you mentioned...) - other then looking straight at the code (which is cool, but is there something else? ) Thanks again! On Wednesday, August 31, 2016 at 5:23:26 PM UTC+3, Jesse Glick wrote: > > On Wed, Aug 31, 2016 at 8:59 AM, <[email protected] <javascript:>> wrote: > > it's > > better to separate it - especially when you have a builder and recorder > in > > one plugin and you'd like to make it a one step in pipeline. > > If there is a reason for these to be separate in a freestyle project, > why should a Pipeline script be obliged to run both in conjunction? > > > In what cases it's advised to separate? and not share code? > > · you need to write an asynchronous step > · you need to use some more advanced Pipeline APIs (e.g., adding an > `Action` to a `FlowNode`) > · there is no way the current `SimpleBuildStep`/`SimpleBuildWrapper` > databinding could work sensibly in a Pipeline script > -- 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/24acf97c-e447-4da6-a1cf-d7575589becf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
