Thanks for the suggestion! Do I understand it correctly, that you are suggesting that we make the base class implement SimpleBuildStep, which will allow it to be used in a pipeline - but will not expose it as a Build step for Freestyle project?
We specifically wanted to allow this to be a Build step in Freestyle projects - do you feel this is ill-advised? There's some teams unable to switch to pipeline for other compatibility reasons, we wanted to allow them to use the upload step as a build step as well. As a next step, we planned to add Download functionality, making this plugin no longer only relevant to post-build - or do you feel that functionality would be better as a separate plugin? On Friday, September 15, 2017 at 10:22:36 AM UTC-4, Jesse Glick wrote: > > On Thu, Sep 14, 2017 at 11:51 AM, 'Alexandra Goultiaeva' via Jenkins > Developers <[email protected] <javascript:>> wrote: > > Does anyone have any suggestions on how to approach this? > > Make it a `Publisher & SimpleBuildStep`. For freestyle projects, it > will appear as a post-build action, which is generally where it should > be (guessing based purely on the name of the plugin). Users with more > complex requirements will be able to run the step from a Pipeline job > whenever and however they like. > -- 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/a35f70a4-cfbd-4ac2-a3f9-5d8edbabe052%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
