pipeline editor plugin

[Michael Neale]

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!

[Kanstantsin Shautsou]

Can it store configuration directly in Jenkinsfile on jenkins side?

[Andrew Bayer]

I believe, from a quick look, that it stores the resulting Workflow script in the job's config.xml.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d7619d30-bb86-4055-a606-1a49b3b58972%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[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.

--
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 jenkinsci-de...@googlegroups.com.

[Oleg Nenashev]

Nice one!
Maybe makes sense to workflow-pipeline-editor-plugin?

суббота, 19 декабря 2015 г., 1:17:47 UTC+3 пользователь Michael Neale написал:

[Baptiste Mathus]

+1 to rename if possible, would make it clearer at first sight. 

Before looking at it when Michael /forked/ it a few days ago, at first I thought it could be related to the Build Pipeline plugin.

--

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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/10f7c58b-4278-470b-9fb2-70a2aa1fbd28%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[Kanstantsin Shautsou]

What is the difference between workflow and pipeline? Or pipeline vs flow? Why not just call it workflow-ui-editor-plugin?

[Michael Neale]

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. 

[Michael Neale]

I actually created a new repo vs a fork (I blame Stephen Connolly for that!), but in retrospect a fork may have been preferable (deleting the upstream of a public repo makes the fork the new root of the fork network). 

[Ioannis Moutsatsos]

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.