groups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Richard Mortimer
Sent: Friday, November 01, 2013 8:51 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo
On 01/11/2013 14:28, Mark Waite wrote:
> It appears you'r
On 01/11/2013 14:28, Mark Waite wrote:
It appears you're not the only one encountering the problem.
https://groups.google.com/d/msg/jenkinsci-users/QDkVHmHnI-U/6cnw4RAvNQIJ
seems to be another example of a similar stack trace
Unfortunately, I have no hint as to the root of the problem.
I to
*Sent:* Thursday, October 31, 2013 9:12 PM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Jenkins 1.537 and git 2.0 code error reported when cloning
> git repo
>
> ** **
>
> By chance, are you trying to use a custom Groovy (or similar) script to
&
2.0 code error reported when cloning git repo
That stack trace seems unrelated to the git plugin and seems to happen after
the clone has completed. It appears the Jenkins maven module is trying to
execute, and is failing. I suspect that happens after the clone is complete.
I created a maven
Subject: Re: Jenkins 1.537 and git 2.0 code error reported when cloning git repo
By chance, are you trying to use a custom Groovy (or similar) script to read
the maven version and store it in a variable?
On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite
mailto:mark.earl.wa...@gmail.com>> wrote
By chance, are you trying to use a custom Groovy (or similar) script to
read the maven version and store it in a variable?
On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite wrote:
> That stack trace seems unrelated to the git plugin and seems to happen
> after the clone has completed. It appears the
That stack trace seems unrelated to the git plugin and seems to happen
after the clone has completed. It appears the Jenkins maven module is
trying to execute, and is failing. I suspect that happens after the clone
is complete.
I created a maven project and had it clone the git-client-plugin fro
Verified that a freestyle project performs a clone without issue. Seems to
be related to the Maven project.
On Thursday, October 31, 2013 3:06:11 PM UTC-6, John Kerr wrote:
>
> I am creating a new installation of Jenkins (1.537) on Ubuntu using the
> git plugin (2.0) and on a maven 2/3 project c
