|
||||||||
|
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/groups/opt_out.
Same issue here using Multiple SCM plugin.
Git 2.0.2.
Git Client 1.6.3.
Multiple SCM 0.3
Started on Feb 25, 2014 4:52:31 PM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision 18e02f062d1dbe081bc9c0b8bac3f5e7b8e85af6 (origin/master)
using GIT_SSH to set credentials
Using strategy: Default
[poll] Last Built Revision: Revision 18e02f062d1dbe081bc9c0b8bac3f5e7b8e85af6 (origin/master)
using GIT_SSH to set credentials
Done. Took 0.89 sec
Changes found
However the actual revisions are:
Revision: 18e02f062d1dbe081bc9c0b8bac3f5e7b8e85af6
Revision: 8f3e5979c556c117905f46dc1811964d70a21998
It looks like somehow the revision of one repo is used for both repos and maybe that kicks off the build.