|
||||||||
|
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/groups/opt_out.
If the Git repository from Gerrit is mirrored to the local Git mirror and the Jenkins job is cloning from the local Git mirror, why not have the Jenkins job monitor the local git mirror?
You could possibly use a post-receive hook for fast detection of new arrivals. That seems like coupling the Jenkins job to the local Git mirror, but launching it from a submission to an unmonitored repository, and expecting it to build a submission which may not yet have arrived in the local Git mirror is unnecessarily asymmetric.
I'm not claiming that your report is not a bug. I think it is a bug, but it seems like you could work around that bug by monitoring the local Git repo with the Jenkins job rather than monitoring the Gerrit repo and cloning the local repo.
Alternately, if clone performance is the issue due to a large repository, you could consider adding an "Advanced clone behaviors" to reference the local Git repo, but clone from the Gerrit repo. That advanced clone behavior has helped significantly reduce my clone times on Linux machines. Unfortunately, I have never foudn a way to make it work on Windows.