maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Gainty <mgai...@hotmail.com>
Subject RE: Build failed in Jenkins: core-it-maven-3-win #1233
Date Fri, 29 Jul 2016 14:04:43 GMT
MG>quick question below


> Subject: Re: Build failed in Jenkins: core-it-maven-3-win #1233
> To: dev@maven.apache.org
> From: cs@schulte.it
> Date: Thu, 28 Jul 2016 17:30:34 +0200
> 
> Can someone take a look, please?
> 
> Error: JAVA_HOME is set to an invalid directory.
> JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64"
> Please set the JAVA_HOME variable in your environment to match the
> location of your Java installation.
> 
> 
> Am 07/28/16 um 17:27 schrieb Apache Jenkins Server:
> > See <https://builds.apache.org/job/core-it-maven-3-win/1233/changes>
> > 
> > Changes:
> > 
> > [schulte] [MNG-5670] guard against ConcurrentModificationException [MNG-6053]
> > 
> > ------------------------------------------
> > Started by an SCM change
> > [EnvInject] - Loading node environment variables.
> > Building remotely on windows-2012-1 (Windows) in workspace <https://builds.apache.org/job/core-it-maven-3-win/ws/>
> >  > git rev-parse --is-inside-work-tree # timeout=10
> > Fetching changes from the remote Git repository
> >  > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/maven.git
# timeout=10
> > Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/maven.git
> >  > git --version # timeout=10
> >  > git -c core.askpass=true fetch --tags --progress https://git-wip-us.apache.org/repos/asf/maven.git
+refs/heads/*:refs/remotes/origin/*
> >  > git rev-parse "origin/master^{commit}" # timeout=10
> > Checking out Revision 53077505a7e9408565ec30a43ad243c41189a94e (origin/master)
> >  > git config core.sparsecheckout # timeout=10
> >  > git checkout -f 53077505a7e9408565ec30a43ad243c41189a94e
> >  > git rev-list 32ce34921cc3d71c4216781de4a574037fad532f # timeout=10
> >  > git rev-parse --is-inside-work-tree # timeout=10
> > Fetching changes from the remote Git repository
> >  > git config remote.origin.url https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
# timeout=10
> > Pruning obsolete local branches
> > Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
> >  > git --version # timeout=10
> >  > git -c core.askpass=true fetch --tags --progress https://git-wip-us.apache.org/repos/asf/maven-integration-testing.git
+refs/heads/*:refs/remotes/origin/* --prune
> >  > git rev-parse "origin/master^{commit}" # timeout=10
> > Checking out Revision 31780e49d00ad5be0dd80ee5b37483f624bbf394 (origin/master)
> >  > git config core.sparsecheckout # timeout=10
> >  > git checkout -f 31780e49d00ad5be0dd80ee5b37483f624bbf394
> >  > git rev-list 31780e49d00ad5be0dd80ee5b37483f624bbf394 # timeout=10
> >  > git branch -a # timeout=10
> >  > git rev-parse "remotes/origin/MNG-2477^{commit}" # timeout=10
> >  > git rev-parse "remotes/origin/MNG-3205^{commit}" # timeout=10
> >  > git rev-parse "remotes/origin/embedder^{commit}" # timeout=10
> >  > git rev-parse "remotes/origin/master^{commit}" # timeout=10
> > [m3-its] $ cmd /c call C:\Windows\TEMP\hudson3181989308987956124.bat
> > 
> > <https://builds.apache.org/job/core-it-maven-3-win/ws/>rmdir> /S /Q <https://builds.apache.org/job/core-it-maven-3-win/ws/.repository>

> > The system cannot find the file specified.
> > 
> > <https://builds.apache.org/job/core-it-maven-3-win/ws/>rmdir> /S /Q <https://builds.apache.org/job/core-it-maven-3-win/ws/apache-maven-3-SNAPSHOT>

> > The system cannot find the file specified.
> > 
> > <https://builds.apache.org/job/core-it-maven-3-win/ws/>exit> 0 
> > [m3-its] $ cmd.exe /C '"f:\jenkins\jenkins-slave\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.1\bin\mvn.cmd
-f maven-3-trunk/pom.xml -DskipTests=true -Dmaven.home.exists.continue=true -DdistributionTargetFolder=<https://builds.apache.org/job/core-it-maven-3-win/ws/apache-maven-3-SNAPSHOT>
-Dmaven.repo.local=<https://builds.apache.org/job/core-it-maven-3-win/ws/.repository>
clean package -B -U -V && exit %%ERRORLEVEL%%"'

MG>can you insert -e -X on mvn.cmd so we can see which plugin is being executed and which
env variables are available e.g.cmd.exe /C '"f:\jenkins\jenkins-slave\tools\hudson.tasks.Maven_MavenInstallation\maven-3.3.1\bin\mvn.cmd
-e -X -f maven-3-trunk/pom.xml -DskipTests=true -Dmaven.home.exists.continue=true -DdistributionTargetFolder=<https://builds.apache.org/job/core-it-maven-3-win/ws/apache-maven-3-SNAPSHOT>
-Dmaven.repo.local=<https://builds.apache.org/job/core-it-maven-3-win/ws/.repository>
clean package -B -U -V && exit %%ERRORLEVEL%%"'MG>re-rerun with -e -X params and
post results here> > Error: JAVA_HOME is set to an invalid directory. 
> > JAVA_HOME = "f:\jenkins\tools\java\latest-1.7-64" 
> > Please set the JAVA_HOME variable in your environment to match the 
> > location of your Java installation. 
> > 
> > Build step 'Invoke top-level Maven targets' marked build as failure
> > Recording test results
> > ERROR: Step ‘Publish JUnit test result report’ failed: No test report files
were found. Configuration error?
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 
 		 	   		  
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message