Jenkins 1.537 and git 2.0 code error reported when cloning git repo

[John Kerr]

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 cloning from a remote git repo as the first thing the job does I get the following ominous error:

Building in workspace /var/lib/jenkins/workspace/project

Fetching changes from the remote Git repository

Fetching upstream changes from ssh://g...@git.com:2222/project.git

using GIT_SSH to set credentials Git access

Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master)

ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com

java.lang.NullPointerException

        at java.io.File.<init>(File.java:251)

        at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)

        at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)

        at hudson.FilePath.act(FilePath.java:1004)

        at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607)

        at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)

        at hudson.model.Run.execute(Run.java:1665)

        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)

        at hudson.model.ResourceController.execute(ResourceController.java:88)

        at hudson.model.Executor.run(Executor.java:230)

project=hudson.maven.MavenModuleSet@6d133151[project]

project.getModules()=[]

project.getRootModule()=null

FATAL: null

java.lang.NullPointerException

        at java.io.File.<init>(File.java:251)

        at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58)

        at hudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41)

        at hudson.FilePath.act(FilePath.java:1004)

        at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607)

        at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562)

        at hudson.model.Run.execute(Run.java:1665)

        at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509)

        at hudson.model.ResourceController.execute(ResourceController.java:88)

        at hudson.model.Executor.run(Executor.java:230)

 

 

 

[John Kerr]

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 cloning from a remote git repo as the first thing the job does I get the following ominous error:

Building in workspace /var/lib/jenkins/workspace/project

Fetching changes from the remote Git repository

Fetching upstream changes from ssh://g...@git.com:2222/project.git

using GIT_SSH to set credentials Git access

Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master)

ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com

[Mark Waite]

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 from https://github.com/jenkinsci/git-client-plugin.git .  That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems.

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

[Jeff]

By chance, are you trying to use a custom Groovy (or similar) script to read the maven version and store it in a variable? 

--

Jeff Vincent
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent

[John Kerr]

No, this was the first job on a new install that was only clone-ing the git repository and then calling the maven pom.

 

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Jeff
Sent: Thursday, October 31, 2013 9:12 PM
To: jenkins...@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 read the maven version and store it in a variable? 

On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite <mark.ea...@gmail.com> wrote:

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 from https://github.com/jenkinsci/git-client-plugin.git .  That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems.

On Thu, Oct 31, 2013 at 3:40 PM, John Kerr <john...@thinktank.net> wrote:

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 cloning from a remote git repo as the first thing the job does I get the following ominous error:

 

Building in workspace /var/lib/jenkins/workspace/project

Fetching changes from the remote Git repository

Fetching upstream changes from ssh://g...@git.com:2222/project.git

using GIT_SSH to set credentials Git access

Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master)

ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/QDkVHmHnI-U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

[John Kerr]

Thank you, I will look deeper into what is happening within the Maven project.

 

From: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Mark Waite
Sent: Thursday, October 31, 2013 8:53 PM
To: jenkins...@googlegroups.com
Subject: Re: Jenkins 1.537 and git 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 project and had it clone the git-client-plugin from https://github.com/jenkinsci/git-client-plugin.git .  That worked on both Debian Wheezy and Debian Jessie using Maven 3 as delivered with those operating systems.

On Thu, Oct 31, 2013 at 3:40 PM, John Kerr <john...@thinktank.net> wrote:

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 cloning from a remote git repo as the first thing the job does I get the following ominous error:

 

Building in workspace /var/lib/jenkins/workspace/project

Fetching changes from the remote Git repository

Fetching upstream changes from ssh://g...@git.com:2222/project.git

using GIT_SSH to set credentials Git access

Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master)

ERROR: Processing failed due to a bug in the code. Please report this to jenkins...@googlegroups.com

 

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/QDkVHmHnI-U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

[Mark Waite]

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.

Mark Waite

[Richard Mortimer]

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 too do not know what the root of the problem is but looking at the
source corresponding to the stack trace it looks like the maven
installation home directory is coming out as null.

line 58 MavenVersionCallable.java

File home = new File(mavenHome);

line 608 MavenModuleSetBuild

MavenInformation mavenInformation = getModuleRoot().act(
new MavenVersionCallable( mvn.getHome() ));

It might be worth checking the global maven configuration to see if
there is anything amiss there.

Regards

Richard

> Mark Waite
>
>
> On Fri, Nov 1, 2013 at 8:25 AM, John Kerr <john...@thinktank.net
> <mailto:john...@thinktank.net>> wrote:
>
> No, this was the first job on a new install that was only clone-ing

> the git repository and then calling the maven pom.____
>
> __ __
>
> *From:*jenkins...@googlegroups.com
> <mailto:jenkins...@googlegroups.com>
> [mailto:jenkins...@googlegroups.com
> <mailto:jenkins...@googlegroups.com>] *On Behalf Of *Jeff
> *Sent:* Thursday, October 31, 2013 9:12 PM
> *To:* jenkins...@googlegroups.com
> <mailto:jenkins...@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 read the maven version and store it in a variable? ____
>
> __ __

>
> On Thu, Oct 31, 2013 at 8:52 PM, Mark Waite

> <mark.ea...@gmail.com <mailto:mark.ea...@gmail.com>>
> wrote:____

>
> 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
> from https://github.com/jenkinsci/git-client-plugin.git . That
> worked on both Debian Wheezy and Debian Jessie using Maven 3 as

> delivered with those operating systems.____
>
> __ __

>
> On Thu, Oct 31, 2013 at 3:40 PM, John Kerr <john...@thinktank.net

> <mailto:john...@thinktank.net>> wrote:____

>
> 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 cloning from a
> remote git repo as the first thing the job does I get the following

> ominous error:____
>
> __ __
>
> Building in workspace /var/lib/jenkins/workspace/project____
>
> Fetching changes from the remote Git repository____
>
> Fetching upstream changes from ssh://g...@git.com:2222/project.git <http://g...@git.com:2222/project.git>____
>
> using GIT_SSH to set credentials Git access____
>
> Checking out Revision f03c2a56f862b3b10013c1e9b0265cb917046a7d (origin/master)____
>
> ERROR: Processing failed due to a bug in the code. Please report this tojenkin...@googlegroups.com <mailto:jenkins...@googlegroups.com>____
>
> java.lang.NullPointerException <http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException>____
>
> atjava.io.File.<init>(File.java:251) <http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3E&entity=method>____
>
> athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.call&entity=method>____
>
> athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.call&entity=method>____
>
> athudson.FilePath.act(FilePath.java:1004) <http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.act&entity=method>____
>
> athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun&entity=method>____
>
> athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method>____
>
> athudson.model.Run.execute(Run.java:1665) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method>____
>
> athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>____
>
> athudson.model.ResourceController.execute(ResourceController.java:88) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>____
>
> athudson.model.Executor.run(Executor.java:230) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>____
>
> project=hudson.maven.MavenModuleSet@6d133151[project <mailto:project=hudson.maven.MavenModuleSet@6d133151[project>]____
>
> project.getModules()=[]____
>
> project.getRootModule()=null____
>
> FATAL: null____
>
> java.lang.NullPointerException <http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException>____
>
> atjava.io.File.<init>(File.java:251) <http://stacktrace.jenkins-ci.org/search/?query=java.io.File.%3Cinit%3E&entity=method>____
>
> athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:58) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.call&entity=method>____
>
> athudson.maven.MavenVersionCallable.call(MavenVersionCallable.java:41) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenVersionCallable.call&entity=method>____
>
> athudson.FilePath.act(FilePath.java:1004) <http://stacktrace.jenkins-ci.org/search/?query=hudson.FilePath.act&entity=method>____
>
> athudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:607) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun&entity=method>____
>
> athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.AbstractBuild$AbstractBuildExecution.run&entity=method>____
>
> athudson.model.Run.execute(Run.java:1665) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Run.execute&entity=method>____
>
> athudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) <http://stacktrace.jenkins-ci.org/search/?query=hudson.maven.MavenModuleSetBuild.run&entity=method>____
>
> athudson.model.ResourceController.execute(ResourceController.java:88) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.ResourceController.execute&entity=method>____
>
> athudson.model.Executor.run(Executor.java:230) <http://stacktrace.jenkins-ci.org/search/?query=hudson.model.Executor.run&entity=method>____
>
> ____
>
> ____
>
> ____

>
> --
> 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

> <mailto:jenkinsci-users%2Bunsu...@googlegroups.com>.
> For more options, visit https://groups.google.com/groups/opt_out.____
>
> __ __

>
> --
> 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

> <mailto:jenkinsci-users%2Bunsu...@googlegroups.com>.
> For more options, visit https://groups.google.com/groups/opt_out.____
>
>
>
> ____
>
> __ __
>
> -- ____

>
> Jeff Vincent
> See my LinkedIn profile at:

> http://www.linkedin.com/in/rjeffreyvincent____

>
> --
> You received this message because you are subscribed to a topic in
> the Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/QDkVHmHnI-U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-use...@googlegroups.com

> <mailto:jenkinsci-use...@googlegroups.com>.
>
>
> For more options, visit https://groups.google.com/groups/opt_out.____

>
> --
> 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

> <mailto:jenkinsci-users%2Bunsu...@googlegroups.com>.

[John Kerr]

This issue was resolved by specifying the Maven version to use in the Jenkins configuration using the "Install automatically" option from Apache instead of using the already installed version of Maven on the system.

To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.