Skip to content

Latest commit

 

History

History
102 lines (81 loc) · 7.13 KB

COMPATIBILITY.md

File metadata and controls

102 lines (81 loc) · 7.13 KB

Plugin Compatibility with Workflow

For architectural reasons, plugins providing various extensions of interest to builds cannot be made automatically compatible with Workflow. Typically they require use of some newer APIs, large or small. This document captures the ongoing status of plugins known to be compatible or incompatible.

Entries list the class name serving as the entry point to the relevant functionality of the plugin (generally an @Extension), the plugin short name, and implementation status.

SCMs

See this guide for making SCMs compatible.

  • GitSCM (git): supported as of 2.3; native git step also bundled
  • SubversionSCM (subversion): supported as of 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
  • DimensionsSCM (dimensionsscm): JENKINS-26165
  • IntegritySCM (integrity-plugin): JENKINS-27140
  • RepoScm (repo): JENKINS-26836
  • teamconcert: JENKINS-27464

Build steps and post-build actions

See this guide for making Builders and Publishers compatible.

Build wrappers

Triggers

Implement Trigger<ParameterizedJobMixIn.ParameterizedJob> and implement TriggerDescriptor.isApplicable accordingly.

Clouds

Do not necessarily need any special integration, but are encouraged to use OnceRetentionStrategy from durable-task to allow flow builds to survive restarts.

  • elasticbox: JENKINS-25978 (could also include build wrapper integration)
  • mansion-cloud: JENKINS-24815
  • mock-slave (for prototyping): JENKINS-25090
  • docker: supported as of 0.8
  • nectar-vmware (CloudBees Jenkins Enterprise): supported as of 4.3.2
  • operations-center-cloud (CloudBees Jenkins Enterprise/Operations Center): RM-2642
  • ec2: known to work as is

Miscellaneous

Custom steps

For cases when a first-class Workflow step (rather than an adaptation of functionality applicable to freestyle projects) makes sense.