Glad to hear it Craig. Glad you enjoyed the "easter egg". One of the ideas is to both make it easy to show the workflow script but also convert it to a regular workflow job (when you need more power).
If you look at the /config.xml (replace /configure with /config.xml) you can see the generated code in the <script> element. In fact Keith Zantow has a react-js version of this editor, which shows both the script below with live changes, and is right in the config page: https://github.com/kzantow/react-pipeline-editor-plugin On Tuesday, January 12, 2016 at 3:57:02 PM UTC+11, Craig Rodrigues wrote: > > This is good stuff. I had fun with this plugin: > https://twitter.com/rodrigc6/status/685371839007305728 > > Some comments: > > (1) It would be nice to somehow be able to see the underlying groovy code > generated by the pipeline-editor. > > (2) It is nice to see "modern" UI design based on "modern" Javascript > components > becoming more integrated with the Jenkins ecosystem! > > -- > Craig > > On Mon, Dec 21, 2015 at 2:18 AM, Michael Neale <michae...@gmail.com > <javascript:>> wrote: > >> (I posted this to jenkins-dev last week, but thought some users here may >> be interested). >> >> An experimental graphical editor for Jenkins Workflow is here: >> https://github.com/jenkinsci/pipeline-editor-plugin (details in the >> README.md). Note very "experimental". >> > -- 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/6d788b75-3d27-4944-9c8f-b7326fe36261%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
