|
||||||||
|
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.
That seems very similar to the case I encountered where the "git show" command ran for many hours at 100% CPU use.
Could you attempt the exact same git command from the command line in the Jenkins workspace on the Windows slave that is trying to execute it from within the plugin?
Open a "git bash" window, change into the Jenkins workspace directory for that job on the slave, and run that exact command. You may find the "git show" command crashes without using the plugin at all. You may find that the "git show" command runs forever without using the plugin at all.
If either of those cases happen, then it indicates that in order to handle your case, the plugin will need to use a different command than "git show" in the isRevExcluded() method. There are discussions in the Jira forums or in the GitHub pull requests offering ideas for alternate ways to answer the same question, but none of the alternatives seem to have been strong enough or complete enough to replace "git show" yet.