s/Workflow/.?/ is of course interesting idea, but i looks like it has the gulf between the two sides. - Freestyle has barrier between build steps and Publishers that constantly causes headache for plugin devs. I tried add SimpleBuildStep support and got other problems (see jenkins PRs) with generic Run objects. - Workflow seems solve many difficult cases, but adds other complexities like new mixed APIs, no input validations, no config migrations. Adding workflow support is impossible without busy @jglick help.
What i really expected - it fixes/improvements in Freestyle (that is really not a "free style" today) with base support for workflow APIs. This should allow having UI features (that was a really feature killer against other CI systems) and allow easily jump to DSLs. New comers will be able to have UI and advanced will be able to pick config. On Tuesday, November 10, 2015 at 3:59:11 PM UTC+3, maciej wrote: > > I think there are two problems with workflow and other script related > plugins: > > 1. There is slim-to-none documentation on Jenkins APIs. There is no > single authoritative place to learn about available interfaces with basic > to advanced examples of their usage. Frankly, I haven't found a good book > about it either. > 2. A killer feature would be to be able to convert build steps (at > least some basic ones) to e.g. Groovy. This would greatly lower the > barrier > of converting from GUI based configuration to code driven job dentitions. > > Regards, > Nux. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7323428c-696e-43d7-936f-6a8211faa751%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
