• Type: New Feature
• Resolution: Unresolved
• Priority: Major
• Component/s: blueocean-pipeline-editor-plugin
• Labels:

  None

[JENKINS-43116] Pipeline playground

James Dumay created issue - 2017-03-27 01:20

James Dumay made changes - 2017-03-27 01:20

Epic Link

New: JENKINS-36291 [ 172300 ]

Michael Neale made changes - 2017-03-28 07:22

Priority

Original: Minor [ 4 ]

New: Major [ 3 ]

Michael Neale made changes - 2017-03-28 07:23

Description

New: Allowing users to interact with the editor without a multibranch project is important. This could be done as a "playground" type of UX - where they can build and run pipelines and iterate rapidly, without having to save changes anywhere. Once they are ready, they are free to export the pipeline as text if they so wish.

James Dumay made changes - 2017-03-29 22:13

Link

New: This issue relates to JENKINS-43118 [ JENKINS-43118 ]

Collapse comment: Gregory PICOT added a comment - 2017-03-31 14:03

Gregory PICOT added a comment - 2017-03-31 14:03

I would like to suggest saving the generated declarative pipeline code into the job directly in "pipeline script" mode to get rid of the manual export to do.
I understand it is not the target, and Jenkinsfile are the way to go, but it would help to get the feature back rapidly

Expand comment: Gregory PICOT added a comment - 2017-03-31 14:03

Gregory PICOT added a comment - 2017-03-31 14:03 I would like to suggest saving the generated declarative pipeline code into the job directly in "pipeline script" mode to get rid of the manual export to do. I understand it is not the target, and Jenkinsfile are the way to go, but it would help to get the feature back rapidly

James Dumay made changes - 2017-05-21 03:06

Link

New: This issue is duplicated by JENKINS-43118 [ JENKINS-43118 ]