Hi Craig - well for pipeline specifically, if you jump on the dev list andrew is trying to flag down some interest in a declarative script: https://groups.google.com/forum/#!topic/jenkinsci-dev/Vsvq6UkIRAQ which should be easy for most.
As for a form based thing, I expect that to be around in any new world (freestyle or simplified pipeline, same result, type in a script). If you have any thought on the plumber thing (which keeps people away from being groovy experts) please lets talk on the dev list. On Friday, May 27, 2016 at 4:59:41 PM UTC+10, Craig Rodrigues wrote: > > Hi, > > The new Jenkins UI looks nice, and will be a big improvement over the > existing UI. > > The original selling point of Jenkins was that even with the simplistic > forms-based UI, > someone could fill out a relatively simple form, and have a continuous > integration pipeline. > I have met people who were general devops and scripting people, and could > use Jenkins quite nicely. > > While I understand the motivation for Pipeline (previously known as > Workflow), I can't say I'm very happy with the results. > > Here are some of the pain points I've encountered with Pipeline scripts: > > - Other than the most trivial of scripts, you need to be a > knowledgable Groovy programmer. For example, to make a global variable, > you need to use a @Field. (What?!) Most scripting and devops people that > I know don't really know Groovy. > - Documentation for Pipeline scripts isn't that great (although it has > definitely been improving). In all honesty, I cannot point a junior > scripting person to write a good Pipeline script for developing a build > Pipeline. > - The durable task plugin which invokes shell commands on Unix, and > batch jobs on Windows goes through an elaborate method for invoking shell > commands. It is very, very difficult to grab the exit status of commands, > stderr, stdout, etc. For a while, these wrappers would do things like not > detect when a command had terminated, etc. (Looks like this has been fixed > now) > - It is very hard to figure out how to cancel a running Pipeline job. > The UI link to "Click here to cancel" a Pipeline job is hidden in the > build > output, and often doesn't work. > > I understand that Jenkins is going through a big transition period. > Hopefully at the end of the road, things will be much better. > However, at this point in time, I would say that in many ways, the current > direction is *worse* than the old way of doing things with the old > Jenkins UI. > The old way has problems, but it was easy to figure out, and didn't have a > lot of these intermediate layers that try to abstract things out, > but make things harder to figure out what is going on. > > -- > Craig > > > > On Thu, May 26, 2016 at 3:21 PM, James Dumay <[email protected] > <javascript:>> wrote: > >> >> Today we’ve made the source code <https://github.com/cloudbees/blueocean> >> available on Github, written a blog post >> <https://jenkins.io/blog/2016/05/26/introducing-blue-ocean/> and created >> a video <https://www.youtube.com/watch?v=3dITffteCD4> explaining the >> project in more detail. We will be posting more updates to both the blog >> and mailing lists when there are more updates to share. >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0fd61f23-140f-4167-bfd5-4771ce97e4f5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
