[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Olivier Kuhn updated JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Change By: Olivier Kuhn (18/Mar/13 10:27 AM) Issue Type: Bug Improvement 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.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
alf1alf commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Support for direct Username/Password config would be great so we do not need to configure each slave - like in the Subversion plugin. 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.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Marcus Klein created JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 14/Mar/13 11:20 AM Description: With the latest update of the git-client-plugin the default behavior is to use the JGit implementation instead of the git command line tool. For the git command line tool I set up HTTP authentication using the file .netrc in the home directory of Jenkins. This does not work anymore with the default JGit implementation. I had to switch back to the git command line tool, which is pretty annoying because the system property needs to be added to the JVM options of every slave. Environment: Debian Squeeze, Jenkins 1.505, running in standalone mode, multiple slaves running on MacOS X and Debian Squeeze Project: Jenkins Priority: Major Reporter: Marcus Klein 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.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Mikkel Bjerg commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin How do I set it so that it uses the original git command line? 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.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Marcus Klein commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin You have to add -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true to the JVM options of the master and every slave. 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.
[JIRA] (JENKINS-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Brant Bobby commented on JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin For people who run Jenkins slaves on Windows as a system service, modify jenkins-slave.xml in the slave's root directory and add the flag to the arguments tag. 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.
