Hi,

I'm currently testing the cache feature of the mercurial plugin, although this is something that I have observed also without such cache enabled. We have a master (that does not performs builds), with several slave nodes which do the actual work of running our project's builds.

The thing is that even though the mercurial plugin detects changes in the repository (as the mercurial polling log reports), the build that is triggered sometimes has an empty list of changes.

And it looks like that it's not "sometimes" really, but with a given pattern I'm starting to see with my tests: when the mercurial plugin detects changes in the repository and triggers a build in a slave that already has a cloned local cache of the repository, then changes are successfully reported as part of the build information. Otherwise, when the build is triggered in a slave without an existing cache for the given repository, for example, that build has an empty list of changes.

Considering that the mercurial plugin always seems to correctly detect that there are new changes that require a build, it's such a nuisance that we have empty changes lists for all those builds.

Regards,
David