Use the "jenkins-pipeline" tag instead for problems using the "Pipeline" (formerly known as Workflow) plugin suite for Jenkins continuous integration.
The Jenkins Pipeline feature, first released in November 2014 (originally called “Workflow”), allows you to define complex orchestrations of build processes in a concise Groovy script. It is not a build tool itself, but a way of letting builds interact with Jenkins-specific features such as slaves, test reports, and so on.
Questions using this tag should be related to this plugin, typically installed as Pipeline and dependencies, and to projects created using the Pipeline option in the New Item page. Tagged questions might cover best usage and idioms, or apparent bugs that you are not sufficiently confident about to immediately file in JIRA, or status of integrations with other plugins, etc.
Not to be confused with the older Build Flow DSL plugin, which Pipeline took as inspiration; nor with the Job DSL plugin, which covers an orthogonal problem (creating multiple similar jobs automatically); nor to the assemblies of “freestyle” projects using various other plugins which Pipeline is intended to supersede in part or in whole (Parameterized Trigger, Copy Artifact, Join, Promoted Builds, Build Pipeline, EnvInject, etc.).
This plugin was formerly known as Workflow plugin. It was renamed to Pipeline in January 2016.
Links:
