Determining plugin compatibility

1 minute read

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

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