I've installed Jenkins recently and have created a free-style project which is linked to a Mercurial repository.
I've installed the Mercurial plugin and set the sources pointing to the correct URL. The user Jenkins is running under can access the repository without issues, and in fact a build right after a workspace cleanup works fine. I'm triggering a build using the URL JENKINS/job/myjob/build?token=mytoken and this works as well. I've also set a commit hook at my repository to hit this URL when a new changeset comes in, and it succesfully triggers the job build. The problem is that after the initial clone, a 'hg pull' from Jenkins itself has no effect on the result. Here's part of the build log right after a push (which triggers the build): [workspace] $ hg showconfig paths.default [workspace] $ hg pull --rev default [workspace] $ hg update --clean --rev default 0 files updated, 0 files merged, 0 files removed, 0 files unresolved Nothing is actually pulled from the repository, even though I _know_ there's more data there to be pulled. If I step into the repository myself and run 'hg inc --rev default', the new changesets are shown. I can even pull the new data myself and trigger a new build on my own, but that's how I hoped it would work.. I'm running Jenkins 1.491 and the Mercurial plugin version is 1.42, but this is happening from the first day I installed Jenkins, a couple weeks ago. How can I make the Mercurial plugin actually pull the new changesets with a new build?
