Determining plugin compatibility

Many source plugins have already added support for the Pipeline feature, while others can be upgraded to support Pipeline through some code changes to utilize some newer APIs.

Supported SCMs

  • GitSCM (git): supported as of 2.3; native git step also bundled

  • SubversionSCM (subversion): supported as of the Subversion Plugin’s v 2.5; native svn step also bundled

  • MercurialSCM (mercurial): supported as of 1.51

  • PerforceScm (p4, not the older perforce): supported as of 1.2.0

Build steps and post-build actions

  • ArtifactArchiver (core)

  • Fingerprinter (core)

  • JUnitResultArchiver (junit)

  • JavadocArchiver (javadoc)

  • Mailer (mailer)

  • CopyArtifact (copyartifact): JENKINS-24887 in 1.34

Build wrappers


  • docker: supported as of 0.8

  • nectar-vmware (CloudBees Jenkins Enterprise): supported as of 4.3.2

  • ec2: known to work as is


  • rebuild: JENKINS-26024

  • build-token-root: JENKINS-26693

  • credentials-binding: withCredentials step as of 1.3

  • job-dsl: implemented in 1.29

Custom steps

  • parallel-test-executor: supported with splitTests step since 1.6

  • mailer: JENKINS-26104 in Pipeline 1.2

The most up to date list on available steps can always be found in the Pipeline snippet generator. The snippet generator is located at the bottom of the configuration page for every Pipeline job. Steps offered by a compatible plugin will appear in the snippet generator once the compatible plugin is installed.

There are some plugins which have not yet incorporated support for Pipeline. Guides on how to add this support, as well as their relevant Jenkins JIRA tickets can be found in the Pipeline Plugin GitHub documentation.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.