It was a version issue with GIT...I had Jenkins pointing to the wrong one.
Thank you all for the help!
A
On Wednesday, January 8, 2014 12:23:33 PM UTC-8, slide wrote:
This is just a guess, but your Git version looks pretty old, so perhaps it
doesn't support the --progress option at all.
I'm having a hell of a time getting Jenkins to work with Git. I'm on
Ubuntu 10.04, Jenkins 1.545, Git 1.7.9.5. I've installed the Jenkins Git
Client 1.6, Jenkins Git 2.0 plugins as well as a few others that I use for
ANT and SVN integrations
I've tried setting up jobs to pull from both a
This is just a guess, but your Git version looks pretty old, so perhaps it
doesn't support the --progress option at all.
On Wed, Jan 8, 2014 at 1:21 PM, Aaron Golub oldbatt...@gmail.com wrote:
I'm having a hell of a time getting Jenkins to work with Git. I'm on
Ubuntu 10.04, Jenkins 1.545,
That is correct. Configure another git in Jenkins, using jgit, and sewer
of that will work in your case without changing your installed git.
Mark Waite
On Jan 8, 2014 1:23 PM, Slide slide.o@gmail.com wrote:
This is just a guess, but your Git version looks pretty old, so perhaps it
doesn't
Aaron,
My apologies for the poorly phrased answer from my phone. There are two
different base implementations of Git which can be used by the Git plugin.
The command line implementation is the default implementation. It assumes
you have git 1.7.10 or newer and requires that git is installed
