PlasticSCM Plugin

Skip to end of metadata
Go to start of metadata

Plugin Information

Plugin ID plasticscm-plugin Changes In Latest Release
Since Latest Release
Latest Release
Latest Release Date
Required Core
2.3 (archives)
Oct 21, 2015
Source Code
Issue Tracking
Pull Requests
Open Issues
Pull Requests
Luis Rodriguez (id: ravelus)
Miguel Gonzalez (id: mig42)
Usage Installations 2014-Nov 61
2014-Dec 70
2015-Jan 63
2015-Feb 58
2015-Mar 64
2015-Apr 56
2015-May 56
2015-Jun 56
2015-Jul 75
2015-Aug 65
2015-Sep 71
2015-Oct 82

This plugin integrates Plastic SCM to Jenkins. This way, users can automatise builds in Plastic SCM using Jenkins.


System configuration

In order to configure the plugin, you need a "cm" executable installed in the Jenkins server machine. Then, please follow these steps:

  1. Open the system configuration page "Manage Jenkins" and navigate to "Configure System".
  2. Then, search the "Plastic SCM" section and enter the path to the "cm" (the command line client).

Job configuration

With Plastic SCM selected in the Source Code Management section of your job, enter the required selector (see picture below). In this textbox you can configure the repository to use and the branch that should be loaded in the workspaces managed by Jenkins. Optionally, select whether the workspace should be cleared between builds; or change the generated workspace name; or add multiple Plastic SCM workspaces to the Jenkins workspace.

The plugin will automatically create the needed workspaces pointing to the specified branch.

You can setup not only branches (which is the normal case), but labels as well as changesets in the selector.

You can also use build parameters in the selector.
Example: Imagine that you define two build parameters in a project:

  • branchname - default value (/main)
  • repositoryname - default value (default)

Then you can use those parameters in the Plastic SCM selector using %parameter_name%. In this case you could write the following selector:

repository '%repositoryname%'
    path "/"
        smartbranch '%branchname%'


The plugin requires that Plastic SCM "cm" command line tool is installed on the master and slave machines.

Plugin version information

This plugin has been developed by Codice Software S.L., owner of the Plastic SCM product.

Visit us at:

Meet us:

Feel the power of merging branches easier than ever with SemanticMerge:

Change log

Version 2.3

  • Added build parameters support in the Plastic SCM selector. Jenkins allows to define build parameters (, and Plastic SCM now can use those parameters in its selector.
    IMPORTANT NOTE: When using parametrized builds, maybe the Poll SCM feature may not work as expected because Jenkins performs the poll with the LAST USED workspace. So maybe the selector is not placed in the branch you expect the poll is performed.
    When using parametrized builds we recommend setting up two Jenkins projects:
    • One for the parametrized build
    • Other, with an static selector to perform the poll.
  • Fixed: When a changeset was a result of a merge, Jenkins was not able to properly present modified elements in 'Changes' chapter.

Version 2.2

  • The Jenkins workspaces now support multiple Plastic SCM workspaces.

Version 2.1

  • Fixed an issue related to the non-ASCII characters included on the date on some cultures such as Korean culture.
  • Support labels and changesets in the Plastic SCM selector.
  • The plugin did not reuse Plastic SCM workspaces correctly when the 'Use update' preference was set. Fixed.

Version 2.0

  • Plugin adapted to Plastic SCM version 4.

Version 1.0

  • Initial version.


plugin-scm plugin-scm Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.