-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Major
-
Component/s: mercurial-plugin
-
Environment:Jenkins ver. 1.526
Auto installer for mercurial to use latest 2.7
Seems jenkins pulls/updates to revision that was last detected by the polling.
This makes it build based on old source if the job is triggered manually (and new commits are in the repo) or if the job is triggered as a post build step in another job.
Second scenario is rather commonly used in our environment but is broken by this behavior.