|
||||||||
|
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.
Based on my analysis so far, I'm certain this is an msys (or Windows?) bug. Jenkins' usage patterns are quite different from a typical developer using git manually and I think that's what's causing issue to show up.
Using Jenkins credentials is an interesting idea! I can see how that would enable ssh to work even with a corrupt environment. Running other git commands from a build script might still run into issues with a corrupt environment though.