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

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

This plugin adds an additional project type that creates sub-projects for each branch using a shared configuration.

Plugin Information

View Multi-Branch Project Plugin (DEPRECATED) on the plugin site for more information.

Table of Contents


This plugin is in its infancy stages. It was designed with simplicity in mind, so you may find that it is not feature-rich. The goal right now is to maintain a production-ready plugin and gather bug reports and new feature requests from the community. Please feel free to open an issue in the GitHub project.

Currently, the plugin offers a single new project type whose configuration mimics that of a standard free-style project. The only difference is that the SCM configuration section utilizes the SCM API Plugin (and so the options may seem somewhat limited compared to the usual SCM options). The project will use this SCM to automatically poll for a list of current branches and sync all the configuration to sub-projects. Each branch has its own sub-project. Sub-projects are just like normal projects, except they can't be configured directly and they are listed on the main (parent) project's page.

Available SCMs

Any SCM plugin that has an implementation that extends the below class from the SCM API Plugin will be available:


Known implementations:

Screenshot - Project Page


  • Depending on the SCM implementation you're using, the branch includes/excludes may or may not work. As of writing, the Git Plugin has configuration fields for includes/excludes, but they are not functional. This commit (currently in 2.3-beta-1) adds the missing functionality. Other SCMs have not been verified (feel free to update this page if you find that SVN or Hg are working or not working).
  • If a branch is deleted from your SCM, or the SCM includes/excludes are modified to remove a branch, the project will always remove that branch's sub-project. If retaining build history for old branches is important to you, you may not want to use this plugin (yet!) since you'll lose that history as soon as the project polls for the branch list.
  • In normal project views, some/most List View columns will not work for this project type.  However, List View columns should work properly in the sub-project list for branches.
  • This project type should be compatible with plugins that you'd see in normal free-style projects, but compatibility can't be guaranteed.  Feel free to open an issue in the GitHub project with your list of installed plugins, your configuration, and any relevant errors or logs.

Change Log

Version 0.1.3 (Oct 30, 2014)

  • Add ability to trigger branch sync via URL with option to allow it anonymously (thanks to Manuel Durán Aguete for the initial commit).

Version 0.1.2 (Aug 29, 2014)

  • Fix project-level permissions when using the "Project-based Matrix Authorization Strategy" security option.

Version 0.1.1 (Aug 13, 2014)

  • Fix configuration issue when restricting project runs to master.

Version 0.1 (Aug 12, 2014)

  • Initial Release
  • No labels