I don't think this is fixed, or else there's been a regression (Jenkins 1.565).

If I have a simple build that uses a BRANCH parameter that defaults to 'master', it will always trigger when notified to look for changes by Stash (via the /git/notifyCommit api), even if there's no changes.

Git polling log looks like this:

Started on Jun 23, 2014 2:01:35 PM
Using strategy: Default
[poll] Last Built Revision: Revision f22fe57691485df88098480c2e56c4e51a68ad67 (origin/master)
using GIT_SSH to set credentials 
 > git ls-remote -h ssh://[email protected]/project/repository.git ${BRANCH}
Done. Took 0.45 sec
Changes found

We're not using wildcards, it's just a simple string parameter with a default setting.

Versions:
Jenkins 1.565
Git client plugin 1.9.1
Git plugin 2.2.1

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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to