Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Template Project on the plugin site for more information.

This plugin lets you use builders, publishers and SCM settings from another project.

A short set up guide

  • Set up a template project that has all the settings you want to share. E.g. you could create one with no SCM filled in, but with all the builders and publishers you want for all your projects. Its best to mark this project as disabled, since you are not actually going to run it.
  • Then set up a concrete project. Configure the SCM as you want. Then select 'use all the publishers from this project' and pick the template project. Ditto for the builders.


  • It may be using some plugins in ways that were not intended. Compatibility with all plugins is not guaranteed.
  • It does not support project actions. That means that links that should be on the project page (e.g. 'latest test results') will not be there.
  • It has had virtually no testing.
  • "Use SCM from another project" may be missing unless you install the multiple-scms plugin. See JENKINS-31712.

To do list

  • Support project actions. This depends on being able to make some changes in jenkins-core in a backward compatible way.
  • Parametrize the templates.
  • (Maybe) Create a separate list of template projects, so you don't have to put them in your main list and can clearly identify them.

Change Log

Version 1.5.1 (Sep 3, 2015)
Version 1.5 (Aug 31, 2015)
  • Expand parameter values, some limitations may apply to SCM (issue #28249)
  • Support Cloudbees folder plugin (issue #24396)
  • Support for build environment variables (issue #24404)
  • Support for Multiple-SCM when using paramater value
Version 1.4.2 (July 9, 2014)
  • Support of dependency declarations interface from included templates.
Version 1.4.1 (Mar 12, 2014)
  • Fixed performance issue when Use SCM is not checked (issue #22150)
Version 1.3 (Aug 15, 2011)
  • Updated SCM proxy for latest Jenkins
Version 1.2 (Feb 11, 2010)
  • Fix Hudson-breaking 1.1 release. (JENKINS-5612)
  • Fix to allow using build steps from a matrix project. (JENKINS-5146)
  • Get form field validators working again.
Version 1.1 (Feb 10, 2010)
  • Update code for more recent Hudson
Version 1.0 (Feb 13, 2009)
  • Initial release


  1. Unknown User (jessicayk)

    To test this plugin I did a template and in the project test configuration I checked the option 'Use publishers from another project' and put the name of the template.

    The plugin worked well only for the Post-build Actions configuration. It didn't work for the Source Code Management, Build Triggers, Build, Build Settings and Build Environment configurations.

    It would be nice using at least the Build Triggers and Build settings too.

    Did I did something wrong or it matches with your tests?


  2. Unknown User (piotr buczek)

    The second limitation is quite painful. This plugin would be great if project actions would be supported! Otherwise I loose important functionality of other plugins.

  3. Unknown User (pushy)

    The plugin sounds very interesting, but the limitations are unfortunately quite painful, as Piotr already pointed out. Also I would really like to have the second and third functionalities on the ToDo List. 

    I noticed that the last release was over a year ago, are there plans for further development?


  4. Unknown User (aartemov)

    I think that "Build notifiers" is a wrong section for this plugin. I would place it for example under "Build tools" or maybe there's another more convenient section.

  5. Unknown User (stormwind)

    The Perforce plugin does not seem to work correctly with jobs that inherit SCM settings.   It will try to use the same workspace as the parent job instead of creating a workspace for the current job.

  6. Unknown User (jforeman)

    I've installed this plugin and I'm not seeing the "use all the publishers from this project" checkbox. Am I missing something? I'm on Jenkins 1.519.

  7. Unknown User (aartemov)

    Mercurial plugin now allows you to specify credentials instead of storing them in .hgrc file. But if in Jenkins job you use "Use SCM from another project", credentials don't work:abort: http authorization required.

  8. Unknown User (brantone)

    Is this plugin being maintained still??

  9. Unknown User (bicschneider)

    I see there are a set of handful commits from the last year, but not released. Can you release the latest version?

    1. Unknown User (brantone)

      Release completed, 1.5.1 is currently available.

  10. Unknown User (perun)

    Why this plugin doesn't support the parametrized-build plugin? I could use so much a feature: Add Parameters from different job!!

    1. Unknown User (brantone)

      Pull requests are always welcome ;) 

  11. Unknown User (abder)

    Hello Every One,

    I m using Jenkins ver. 1.642.4

    I have installed the plugin, created the template Job, but I don't have the option Use SCM from another project in the Source Code Management

    for a new Job,

    Can you help please?

    Thanks in advance

    1. Unknown User (brantone)

      Anything showing up in Jenkins logs?? Feel free to submit a ticket with repro steps and 

  12. Unknown User (chrisnelsonpe)

    How is this plugin better than or different from the Copy Project plugin?

    1. Unknown User (brantone)

      It doesn't require copying a project, but rather uses pieces ... think of it like having a set of libraries and each project can just call those libs.