Issue Type: Bug Bug
Assignee: Nicolas De Loof
Attachments: jenkins.err.log, jenkins.out.log, jenkins.wrapper.log, no_cred_nullpointerexception.txt
Components: git
Created: 16/Dec/13 1:13 PM
Description:

We're trying to upgrade from Jenkins 1.533, Git Plugin 1.5.0, and Git Client Plugin 1.3.0 to the latest without luck. Jenkins simply will not clone Git repositories.

Cloning via https://mydomain.com/repo.git using command line Git works perfectly on the machine that has Jenkins installed (msysgit and gitcredentialwinstore). This used to work on the old Jenkins/Git plugin too.

The new Jenkins/Git Plugin had the following issues:

1. Failed to clone because of invalid certificate (despite command line git working). Seems like the plugin accesses https:// directly despite being told to use the command line Git. We now have a valid cert on the server however.

2. If using user/password credentials, Jenkins reports "status = 401" on the job configuration. Have tried with both DOMAIN\user and user (without domain specification).

3. When I select "NONE" as credentials (which works with the command line git, because of gitcredentialwinstore), I get a NullPointerException. (And a big fat error page in the middle of the configuration screen). I also get this exception with a simple https://github.com/someproject/

Environment: OS: Windows Server 2008 R2
Git Protocol: https
Git server: SCManager (or even github).
Jenkins 1.544
Git Client plugin 1.5.0
Git Plugin 2.0
Project: Jenkins
Priority: Major Major
Reporter: Lars Christensen
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.

Reply via email to