[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite closed JENKINS-20643 as Fixed Git plugin does not work with Visual Studio Online Change By: Mark Waite (01/Apr/14 4:20 AM) Status: Resolved Closed 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/d/optout.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite resolved JENKINS-20643 as Fixed Git plugin does not work with Visual Studio Online After no response from the original submitter suggesting any other reasons other than needing to define credentials, and use them, I'm marking this as fixed. Change By: Mark Waite (01/Apr/14 4:19 AM) Status: Open Resolved Resolution: Fixed 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/d/optout.
[JIRA] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite commented on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my TFS repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report. In both those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. 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] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite updated JENKINS-20643 Git plugin does not work with Visual Studio Online Change By: Mark Waite (19/Nov/13 1:31 PM) Priority: Blocker Major 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] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report. In both those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. 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] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. 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] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. The multi-configuration job which I defined with https://markewaite.visualstudio.com/DefaultCollection/_git/JENKINS-20643 as the repository and my Visual Studio Online credentials was able launch on a Windows Home Server 2011 (initial workspace), and cloned successfully on Windows 7, Windows 8.1, Windows Home Server 2011 with x64 JRE, Windows Home Server 2011 with x86 JRE, Debian Wheezy, and Debian Jessie. 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] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. The multi-configuration job which I defined with https://markewaite.visualstudio.com/DefaultCollection/_git/JENKINS-20643 as the repository and my Visual Studio Online credentials was able launch on a Windows Home Server 2011 (initial workspace), and cloned successfully on Windows 7, Windows 8.1, Windows Home Server 2011 with x64 JRE, Windows Home Server 2011 with x86 JRE, Debian Wheezy, and Debian Jessie. I used the git command line implementation for all the job definitions up to this point. When I switched to use the JGit implementation for a new multi-configuration job definition, the clone hangs on both Windows Home Server 2011 and on Windows 7 slave agents. That needs more investigation and a separate bug report. 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] [git] (JENKINS-20643) Git plugin does not work with Visual Studio Online
Mark Waite edited a comment on JENKINS-20643 Git plugin does not work with Visual Studio Online I can duplicate the problem and believe there is a work around. If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job. If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report until I add a global credential for Visual Studio Online. Once I've added the global credential for Visual Studio Online and referenced it in the plugin definition for that job, then the "ls-remote" message disappears on the Linux machine I'm using as master server. It may yet happen on a Windows server. In each of those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job. I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition. The multi-configuration job which I defined with https://markewaite.visualstudio.com/DefaultCollection/_git/JENKINS-20643 as the repository and my Visual Studio Online credentials was able launch on a Windows Home Server 2011 (initial workspace), and cloned successfully on Windows 7, Windows 8.1, Windows Home Server 2011 with x64 JRE, Windows Home Server 2011 with x86 JRE, Debian Wheezy, and Debian Jessie. I used the git command line implementation for all the job definitions up to this point. When I switched to use the JGit implementation for a new multi-configuration job definition, the clone hung on both Windows Home Server 2011 and on Windows 7 slave agents. That needs more investigation and a separate bug report. 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.
