I would say that a pipeline has to process, filter or transform artifact(s) in a series of steps/stages. So in a pipeline there is a pretty clear definition of an input/output. A workflow may not have such clear definition and instead is more of the orchestration of actions to achieve a desirable outcome.
On Sunday, December 20, 2015 at 6:49:27 PM UTC-5, 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/4a45aa3e-4004-412f-ae7c-ab00936ba8c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
