> > Then make a separate `Builder` (which would be the more natural one to > mark as a `SimpleBuildStep` as well, if you have to choose). Obviously > most implementation can be shared via a utility class. >
Thanks! This is exactly what I've tried to do in the code I've linked to at the beginning. I've created a separate Builder that utilized existing implementation. My original question was about whether I could reuse the (nested) jelly files as well, and if the framework was flexible enough to allow me to make the config.jelly display slightly differently in the Post-Build Step and Build Step. > As a general matter I recommend developers stay away from overly > specific plugin features like “upload this to Google Storage if the > build is stable” or “download this from Google Storage and unzip to > the workspace”. Agreed, the download capability we're planning is pretty generic. Any post-processing can be done by e.g., a bash step. -- 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/fe65d708-016d-45ad-bcde-b192a1ea5322%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
