If you're new to git, then I'd suggest the following steps to have some quick, positive experiences that will also confirm your Jenkins installation is working reasonably. Those steps may also help you identify areas where you need to fine tune or improve your Jenkins installation.
1. Add JGit as a git installation from the "Manage Jenkins", "Configure System", "Git installations" 2. Confirm the JGit installation works by creating a job which clones a publicly accessible git repository (either git:// github.com/jenkinsci/git-client-plugin.git or https://github.com/jenkinsci/git-client-plugin). That job will show you that your git installation is sufficient to clone the repository 3. Install command line git on your Jenkins server and slaves 4. Confirm the command line git installation works by creating a job which clones a publicly accessible git repository (same repositories as were used for JGit) 5. Confirm JGit works with your repository by creating a job which clones your private repository 6. Confirm command line git works with your repository by creating a job which clones your repository Those steps should give you several initial successes with Jenkins and give you confidence that you have the git plugin working at its most fundamental level. To learn more about Git, there are youtube videos, online books, and more. Mark Waite On Thu, Sep 10, 2015 at 12:40 PM <angel.willi...@centrallogic.com> wrote: > Mark, > > Can you supply a commandline to use.. that is how new to GIT I am and if > you know a good site for details on GIT that I can get up to speed on it. > > > On Wednesday, September 9, 2015 at 5:50:57 PM UTC-6, Mark Waite wrote: > >> Some of the things you can test to see if any of them help: >> >> 1. Use a command line git version that is new enough to support >> credentials (1.8 or newer is enough, 1.7.10 is also reported to work) >> 2. Confirm you can clone your repository using command line git and >> the specific URL, username and password >> 3. Add a Jenkins credential with username and password, then use that >> credential with a Jenkins job to see if the repository is cloned >> 4. Confirm you can clone your repository using command line git and >> the URL >> >> https://username:passw...@company.visualstudio.com/DefaultCollection/_git/Company/ >> 5. Try a test job with URL >> >> https://username:passw...@company.visualstudio.com/DefaultCollection/_git/Company/ >> 6. Try a test job with the prior credential and URL >> https://usern...@company.visualstudio.com/DefaultCollection/_git/Company/ >> >> <https://username:passw...@company.visualstudio.com/DefaultCollection/_git/Company/> >> >> Mark Waite >> >> On Wed, Sep 9, 2015 at 5:12 PM <angel.w...@centrallogic.com> wrote: >> > How do I allow jenkins to access GIT source from the VSOnline GIT source? >>> >>> https://company.visualstudio.com/DefaultCollection/_git/company >>> >>> Failed to connect to repository : Command "C:\Program >>> Files\Git\bin\git.exe -c core.askpass=true ls-remote -h ' >>> https://company.visualstudio.com/DefaultCollection/_git/Company HEAD" >>> returned status code 128: >>> stdout: >>> stderr: fatal: Authentication failed for ' >>> https://company.visualstudio.com/DefaultCollection/_git/Company/ >>> >>> I set up an alternate authentication method on my account in VSOnline >>> but I still can't access it. >>> >>> Someone suggested I use a commandline option in a build step but am >>> unfamiliar with how to do that as well.. >>> >>> Any help would be greatly appreciated. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> >> To unsubscribe from this group and stop receiving emails from it, send an >>> email to jenkinsci-use...@googlegroups.com. >> >> >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/e2d491cb-34e4-4729-b0a5-d9db22979bbe%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/e2d491cb-34e4-4729-b0a5-d9db22979bbe%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/32c5364d-e094-4977-9a9f-3e796237580c%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/32c5364d-e094-4977-9a9f-3e796237580c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGY9a6k6D2kYL-UEieFCN68%3D0A8RmcXO3dbs-SLyacsYQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
