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 70 Next »

Plugin Information

View Pretested Integration on the plugin site for more information.

Developed by

Sponsored by

Introduction

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).

References

Job configuration

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
Esben Skaarup
Andreas Frisch

Notes

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:

Correct
Incorrect

Issues

type key summary

Data cannot be retrieved due to an unexpected error.

View these issues in Jira

Changes

Version 2.1.2:

  • Implemented logging tracing

Version 2.1.1:

Version 2.1.0:

  • 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

Version 2.0:

  • Git integration is now supported

Version 1.1:

  • 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

Version 1.0:

  • Release of the first stable version
  • No labels