Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Removed some old text that apparently was not deleted


The workflow is adapted from the personal branch version of the branchy approach described in [\\]

1. A named branch is used as the team integration branch (defaults to 'default'). 


For Git and Mercurial, it is possible to uniquely identify a commit by a hash value. It is possible to parameterise "org.jenkinsci.plugins.pretestedintegration.Commit" in order to use a custom class or type which uniquely identifies the commit.

NB! This is a temporary version of the plugin using a cloning approach. A new version using branching wil be released shortly

This plugin lets Jenkin manage a repository – keeping it in a clean state by only integrating changesets which build successfully. Builds – and thus repository updates – are triggered when developers push to another designated repository.