|
||||||||
|
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.
@Steffen
I tried to reproduce this on my local machine.
1) I downloaded a fresh windows installer and installed jenkins 1.560 on my local machine. By default the master comes with 2 built in executors
2) Installed Git 2.2.1 plugin
3) Installed the multiple SCM plugin (0.3).
4) Then i created a job which checks out our local testing repository located here: https://github.com/Praqma/praqma-playground, polling interval set to 1 minute.
What i saw when doing this was that a new job was put in queue and a new build was created after waiting 1 minute.
I Then started creating another commit, committed and saw that it worked again..I also tried deleting workspaces and builds, and commiting again and saw that it once again would kick off.
Do you have any special settings configured for your git plugin? Anything that might help me reproduce this?