The Pretested Integration Plugin offers a branchy approach to pretested integration (also known as pre-tested commits), which upholds the invariant; that for a specific branch, known as the integration branch, all commits have been verified.
The plugin rely on the SCM plugin to establish the workspace and then take over to do the integration and later make the decision wether to like and commit the result or hate and discard it. To get a comprehensive introduction to how the plugin relies on the SCM plugin please read the blog post at the JOSRA: Pretested Integration Plugin.
The short version is:
Set the branch specifier to the pattern you'd like to trigger the integration we recommend origin/ready/**:
In the current version of the pretested integration plugin we also rely on the folloing two beaviours to be added to the Git SCM plugin:
We are offering a one-click-configuration. So after the plugin is installed simply go to the job, enable pretested integration by clicking 'Use pretested integration'. Everything should now be configured and work out of the box, if you integration branch is master.
Ronni Elken Lindsgaard
Alexander Winther Uldall
The plugin will automatically add a publisher to the job when the job is first executed, when remvoing pre-tested integration from your job, remember to delete the publisher as well.
When using the MultipleSCMs plugin you are only allowed to specify one instance of the git plugin. You can then add multiple repositories like so: