• Browse
  • Pages
  • Blog
  • Labels
  • Attachments
  • Mail
  • Advanced

  • People Directory
  • Keyboard Shortcuts
  • Confluence Gadgets
• Kohsuke Kawaguchi
  • Recently Viewed

  • Profile
  • Network
  • Labels
  • Watches
  • Drafts
  • Settings

  • Log Out

1. Dashboard
2. Jenkins
3. Plugins
4. Mercurial Plugin

Mercurial Plugin

{0}."> {0}-{1} of {2} pages containing {3}.">

Skip to end of metadata

• Page restrictions apply
• Attachments:1
• Added by Kohsuke Kawaguchi, last edited by davidmc24 - on Nov 11, 2012  (view change)
• show comment hide comment

Comment: Add environment variables section

Go to start of metadata

Jenkins Home Mailing lists Source code Bugtracker Security Advisories Donation Commercial Support Wiki Site Map Documents Meet Jenkins Use Jenkins Extend Jenkins Plugins Servlet Container Notes

This plugin integrates the Mercurial version control system with Jenkins. Plugin Information Plugin ID mercurial Changes In Latest Release Since Latest Release Latest Release Latest Release Date Required Core Dependencies 1.42 Nov 06, 2012 1.424 Source Code Issue Tracking Maintainer(s) GitHub Open Issues Jesse Glick (id: jglick) Mirko Friedenhagen (id: mfriedenhagen) Kohsuke Kawaguchi (id: kohsuke) David M. Carr (id: davidmc24) Usage Installations 2011-Nov 2341 2011-Dec 2320 2012-Jan 2505 2012-Feb 2673 2012-Mar 2778 2012-Apr 2804 2012-May 2892 2012-Jun 2819 2012-Jul 2946 2012-Aug 2986 2012-Sep 3030 2012-Oct 3235 With this plugin, you can designate a Mercurial repository as the "upstream" repository. Every build will then run something like hg pull -u to bring the tip of this upstream repository. In a similar manner, polling will check if the upstream repository contains any new changes, and use that as the triggering condition of the new build.  This plugin is currently intended to support Mercurial 1.0 and later. Viewers included are bitbucket, fisheye, google-code, hgweb, kiln, and rhodecode. Push Notifications As of version 1.38 it's possible to trigger builds using push notifications instead of polling. In your repository's .hg/hgrc file add: [hooks] commit.jenkins = wget -q -O /dev/null <jenkins root>/mercurial/notifyCommit?url=<repository remote url> incoming.jenkins = wget -q -O /dev/null <jenkins root>/mercurial/notifyCommit?url=<repository remote url> This will scan all the jobs that's configured to check out the specified URL, and if they are also configured with polling, it'll immediately trigger the polling (and if that finds a change worth a build, a build will be triggered in turn.) This allows a script to remain the same whe