Skip to end of metadata
Go to start of metadata

Plugin Information

View Pipeline on the plugin site for more information.

A suite of plugins that lets you orchestrate automation, simple or complex. See the Jenkins website for more details and documentation.
Documentation on the Jenkins site:

Other information about Pipeline is available in GitHub. Quick links:

Formerly known as the Workflow plugin. Originally inspired by the Build Flow Plugin.

Changelog

2.6 (Oct 3, 2018)

  • Updated dependencies.

2.5 (Feb 01, 2017)

2.4 (Sep 21, 2016)

2.3 (Aug 31, 2016)

  • Updated dependencies.

2.2 (Jun 22, 2016)

  • Updated dependencies.

2.1 (May 03, 2016)

2.0 (Apr 05, 2016)

18 Comments

  1. It's an interesting extension that provides a lot of functionality that has been missing, but without the visualization of the workflow, it's doesn't really feel like all that compelling an alternative to the existing plugins.

    1. CloudBees offers a visualization plugin for workflows:

      1. Is this plugin available separately somehow? Or do I have to buy the Jenkins Enterprise to have this available?

        1. That's a closed-source plugin created by CloudBees; you'd have to ask their sales people.

          Update, Jan 2016: The plugin is intended to be open-sourced at some point; see JENKINS-31154.

          1. Yes. Kohsuke announced this as part of his presentation on Jenkins 2.0. The OSS repo has been created and we will moving the code there soon. We will put out a blog when the plugin and its code are released into OSS.

        2. The plugin has just been open sourced, but it's still in "alpha" stage: https://github.com/jenkinsci/pipeline-stage-view-plugin

  2. The release notes link appears to be an empty list (for 1.10 -> 1.10.1), presumably because it's only showing the changes for the aggregator. Can that be fixed?

  3. The snippet generator does not show how to code for all given plugins (understandably).  Is there a way to add to this list?

    For example, it would be common to publish JUnit result report:

    step([$class: 'JUnitResultArchiver', testResults: '**/reports/unittest/TEST-*.xml'])
    

    Is there a comparable one for Publishing Cobertura reports:

    step([$class: 'Cobertura???', coverageResults: '**/reports/coverage/xml/*.xml'])
    

    Or others?

    1. Learning on the fly here. I see that JUnitResultArchiver implements SimpleBuildStep, whereas the CoberturaPublisher extends Recorder.

      Suggestions on how to publish Cobertura reports with the Pipeline?

      1. Hi Paul,

        Please use the users mailing list, or the #jenkins IRC channel for questions. You're far more likely to get support there. Few to no people watch the plugins comments in my experience.

        Cheers

  4. Hi,

    When using the multi branch feature there are onyl 2 build triggers in the job (periodically). The jobs that get created by the branch indexing do not have any build trigger configuration and i cannot even manually change it. How are the branch jobs supposed to be triggered?

  5. Is the Getting Started up to date? It says I will require Jenkins version 1.609.1+, but the only plugin I can find in the plugin manager that is simply named "Pipeline" says:

    Warning: This plugin is built for Jenkins 1.642.1 or newer. It may or may not work in your Jenkins.
    Warning: This plugin requires dependent plugins that are built for Jenkins 1.642.1 or newer. The dependent plugins may or may not work in your Jenkins and consequently this plugin may or may not work in your Jenkins.
    Am I looking at the wrong plugin in the manager?

  6. Can you please upgrade the workflow-cps to latest version, 2.19?

  7. Is there an API to create the Pipeline via Powershell REST API calls?  If so, where is the documentation for it?

  8. Jenkins jobs do not normally (actually I have never seen it before with any plugins) trigger a run when you change and save job configuration.

    This plugin does so with Pipeline Items (jobs) as well as Multibranch Pipeline Items (jobs). Even a simply change of job description will trigger a run! Very annoying.

    Is there any way to disable autorun on config save with this plugin, and if not, could You please remove this "feature"?

  9. Could you upgrade the dependencies to the latest versions? My Jenkins instance displays warnings about some of them. To be more specific:

    • workflow-step-api to 2.12
    • pipeline-build-step to 2.5.1
    • pipeline-input-step to 2.8
  10. I have noticed that the Build Stats Plugin fails to collect data from Pipeline builds.  Is there a way to get build information from a pipeline build included in those statistics?

  11. can the dependent plugins be updated alone?