Hey Mark, I was trying to play it safe, so I uninstalled the existing git-plugin, and then installed the version you pointed to on dropbox. I can see it listed under installed plugins as version "1.16.2-SNAPSHOT (private 744b9fe-mwaite), however, git no longer shows up as an option (no radio button) under "Source Code Management" when configuring my job. What did I do wrong here?
Thanks, --thom On Saturday, February 14, 2015 at 8:59:58 PM UTC-8, Mark Waite wrote: > > I spent some time this weekend writing tests and evaluating possible code > changes to ease diagnosis of git command line failures. > > If you're willing to "test drive" an unreleased version of the > git-client-plugin (which encapsulates the command line git calls used by > the git-plugin), I'd like to use your case to evaluate the impact of the > changes. > > The unreleased version has passed its automated tests on multiple Windows > versions, multiple Linux versions, and multiple git versions. > > You can download and install that unreleased version of the plugin from: > > https://www.dropbox.com/l/0nHPJ7eTaLOJnmgUfVT8bp > > Mark Waite > > On Fri, Feb 13, 2015 at 4:01 PM, Thom Ellis <[email protected] > <javascript:>> wrote: > >> I'm brand new to Jenkins, and just trying to set up a simple test to try >> and play around with it a bit, but I'm hitting a snag, and not sure what >> the issue is. I have a very basic git repository, and which I used to >> create a bare shared repository, and I'm just pointing directly to the >> repository itself in my configuration. Whenver I run a build job however I >> get the following: >> >> Started by user anonymous >> Building in workspace /var/lib/jenkins/workspace/test-default >> Cloning the remote Git repository >> Cloning repository file:///home/repos/test.git >> > /usr/bin/git init /var/lib/jenkins/workspace/test-default # timeout=10 >> ERROR: Error cloning remote repo 'origin' >> ERROR: Error cloning remote repo 'origin' >> Finished: FAILURE >> >> I'm able to clone the repo just fine from the command line, and I was >> also able to clone it just fine by creating a new build job where instead >> of linking to git, I just execute the clone command itself in Jenkins, with >> no issues. Anyone have any tips/ideas? With the limited error output, I'm >> not really sure what else to check. >> >> Thanks in advance! >> >> -- >> 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 [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/bcdd2e54-3afa-4f60-9881-8c8b83eac7b6%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/bcdd2e54-3afa-4f60-9881-8c8b83eac7b6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Thanks! > Mark Waite > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d0e670e6-8dba-46c9-b81b-5da6496e5257%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
