View Pretested Integration on the plugin site for more information.
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.
This plugin is developed by Praqma and sponsored by Atmel - It's maintained in the scope of Joint Open Source Roadmap Alliance (JOSRA).
- For more background information and a discussion on the different merge strategies available please read the blog post at the JOSRA: Pretested Integration Plugin.
- For a Paper on how to implement at complete flow of automated continuous delivery - including pretested integration read the white paper: CoDe:U Git Flow - a Continuous Delivery Approach.
- To follow the roadmap for this plugin see the Trello board.
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:
- Clean af checkout
- Prune stale remote-tracking branches
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.
Code contributions were initially made by Computer Science students at University of Copenhagen as part of a study project
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.
Using the MultipleSCMs plugin (comming in 2.2.0)
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:
- Implemented logging tracing
- Bugfix for running on slaves (JENKINS-24844)
- Protected master branch (Plugin tries to delete origin/master JENKINS-24286)
- Re-using last commit message in accumulated strategy (Improve commit message JENKINS-24285)
- Removed the "origin" from the description (JENKINS-24284)
- When squashing commits, now using author from tip of branch (JENKINS-24443)
- Additional tests added as well
- Git integration is now supported
- Dependency of Mercurial plugin set to 1.39 due to previous failure to trigger on merge commits
- Removed UI elements that should not have been there
- Release of the first stable version