On Mon, Feb 9, 2015 at 8:06 AM, tommy.warchol <[email protected]> wrote: > Am I expecting something impossible?
I think so. Master-based polling works when Jenkins send send the equivalent of a git-ls-remote command to the server, which gives back a commit hash of the tip of the branch. It can compare that to the last-built commit; if different, schedule a build. But if you want to know *anything* about any of the intermediate commits—files changed, authors, message—in order to decide whether to trigger a new build, you need to find a checkout, actually pull those commits, and inspect them. Compare ‘svn log <URL>’ which can get such metadata over the wire. In the case of the Mercurial plugin, if you enable the “caches” feature, then the pull from remote is done on a naked clone on the master, so no workspace is required for polling even though Mercurial also provides no way to get such metadata without pulling full commit objects. I have suggested that the Git plugin could copy this trick. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3kcMs1MR4w4LUFpacAK%3DiJykPjsri6LcUyazkuaYLPbA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
