[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT

Mon, 14 Jul 2014 11:27:14 -0700

Don Ross commented on Bug JENKINS-20427

I am seeing this same behavior after upgrading from 1.1.21 to 2.2.2.

I noticed that the default is now to always use Fast Remote Polling; in my production environment I have this option turned off. So, I enabled 'Force polling using workspace', and I am now seeing a different message (but the same behavior of false changes being found), as follows:

Started on Jul 14, 2014 1:16:38 PM
Polling SCM changes on slave-host-name
Using strategy: Default
[poll] Last Built Revision: Revision 44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f (origin/release_branch)
 > git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repositories
 > git config remote.origin.url ssh://build@gitserver/git/product.git
Fetching upstream changes from ssh://build@gitserver/git/product.git
 > git --version
 > git fetch --tags --progress ssh://build@gitserver/git/product.git +refs/heads/*:refs/remotes/origin/*
Polling for changes in
 > git rev-parse "origin/release_branch^{commit}"
 > git rev-parse "release_branch^{commit}"
 > git log --full-history --no-abbrev --format=raw -M -m --raw 44bfcc7cdf27d192f1d8e29a2863ff3c3940cb6f..9f74e3057c7fb30d2c001f886e394d5bea0271a
Done. Took 1.8 sec
Changes found


It is interesting to me that the '9f74e3' commit ID in that git log command is the commit immediately before the '44bfcc7' commit.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to