yes the nomenclature is currently confusing. Currently, I *believe* people say they use the "workflow" to build "pipelines" (there are other ways to build pipelines). workflow is provided via the Jenkins Workflow plugin (and there are other plugins related to this).
workflow-ui-plugin would be ok, but there could well be other ways to edit workflow in a UI than just this (this one has a pipeline-like visualisation), but all using the underlying workflow plugin. Confused? hehehe. On Monday, December 21, 2015 at 10:49:27 AM UTC+11, Kanstantsin Shautsou wrote: > > What is the difference between workflow and pipeline? Or pipeline vs flow? > Why not just call it workflow-ui-editor-plugin? > > On Saturday, December 19, 2015 at 11:32:38 AM UTC+3, Oleg Nenashev wrote: >> >> Nice one! >> Maybe makes sense to workflow-pipeline-editor-plugin? >> >> суббота, 19 декабря 2015 г., 1:17:47 UTC+3 пользователь Michael Neale >> написал: >>> >>> No, not at the moment. The workflow script is stored in the config.xml >>> (the same as if it was edited in the text area), but also a json blog is >>> stored with the information to drive the GUI (names of things and so on). >>> Not sure if that is a good permanent solution but it was convenient to >>> start with. >>> >>> On Sat, 19 Dec 2015 at 3:21 AM, Kanstantsin Shautsou < >>> [email protected]> wrote: >>> >>>> Can it store configuration directly in Jenkinsfile on jenkins side? >>>> >>>> >>>> On Friday, December 18, 2015 at 7:08:37 AM UTC+3, Michael Neale wrote: >>>>> >>>>> I wanted to introduce a bit of an experimental plugin for workflow: >>>>> https://github.com/jenkinsci/pipeline-editor-plugin >>>>> >>>>> (details in the README.md). >>>>> >>>>> The basic idea is to support a very small subset of workflow, which is >>>>> stored in a model, and outputs executable workflow script (you can try it >>>>> out). >>>>> Obviously (when you see it) it is fairly js heavy, but this was >>>>> enabled but the handy tooling and packaging via: >>>>> https://github.com/tfennelly/jenkins-js-modules. >>>>> >>>>> This is likely to change quite a bit, but I am interested in >>>>> ideas/thoughts (I believe the first issue that someone who discovered the >>>>> repo was "why not use react" - which is certainly being worked on!). >>>>> I am also interested in what benefits people might see for users of >>>>> Jenkins, learning workflow, or wanting to see a stage-like view as they >>>>> edit (this may not be you, but may be someone you know). >>>>> >>>>> Cheers! >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-dev/fZfWapYbN6o/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/d7619d30-bb86-4055-a606-1a49b3b58972%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/d7619d30-bb86-4055-a606-1a49b3b58972%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> -- 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/90ae183d-417a-447e-b76f-a93376f26e6d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
