Unfortunately freestyle build is not freestyle. I guess because of workflow nobody interested in merging/enhancing other job types. There is a workaround by using any-build-step/flexible publisher plugins that expose types vice versa.
On Monday, December 12, 2016 at 7:18:36 PM UTC+3, Dan Alvizu wrote: > > Hi, > > I'm working on the jira-ext plugin, which updates JIRA tickets as a > hudson.task.Builder, which means it shows up in the drop-down of build > steps. I would also like to have it show up in the list of post-build > steps, which I understand means I must extend a hudson.task.Publisher. > > I can just copy-pasta this into another class and have that one extend > hudson.task.Publisher, but that seems wrong. The implementation is > essentially the same. Is there a smarter way of doing this? > > Thanks! > -- 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/6e9710ee-86df-40f1-9bbf-9d87e9930ae1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
