Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


This plugin lets Jenkin manage your company truth 'upstream' a repository – keeping it in a clean state by only pushing changesets which build successfully. Builds – and thus updates – are triggered when developers push to a specific designated repository.


In Jenkins each job can be configured to use Pretested Integration from the job configuration page. Once selected, Jenkins will start building the job in question every time a developer pushes change to the repository defined in the plugin setup page (the staging repository). Whether or not this repository already exist, it is important to click 'Make/update repository': if the repository does not exist it will be created at the given path and a repository hook will be added. If the repository already exists, the hook will be added. This repository hook is responsible for starting builds, why this step is important. Refer to the supplied screenshot for a visual example.

Image Added

At this point client repositories should change their default configuration for push-requests to point to this 'downstream' repository.

Image Removed

Known Issues

Currently when using the 'Make/update repository' button, backslashes are removed from the hgrc file of the staging repository. Users should verify that their paths and other variables in the hgrc file are correct after using the button.


No changes yet.