See <https://builds.apache.org/job/Vysper/3/display/redirect>
------------------------------------------ Started by an SCM change [EnvInject] - Loading node environment variables. Building remotely on H33 (ubuntu xenial) in workspace <https://builds.apache.org/job/Vysper/ws/> No credentials specified > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url > https://gitbox.apache.org/repos/asf/mina-vysper.git # timeout=10 Fetching upstream changes from https://gitbox.apache.org/repos/asf/mina-vysper.git > git --version # timeout=10 > git fetch --tags --progress > https://gitbox.apache.org/repos/asf/mina-vysper.git > +refs/heads/*:refs/remotes/origin/* Seen branch in repository origin/0.6 Seen branch in repository origin/0.7 Seen branch in repository origin/master Seen branch in repository origin/mina2.0_migration Seen branch in repository origin/nbxml-old Seen branch in repository origin/nbxml-sax Seen branch in repository origin/s2s Seen branch in repository origin/xep-0313 Seen branch in repository origin/xep0114 Seen branch in repository origin/xep0144 Seen 10 remote branches > git show-ref --tags -d # timeout=10 Multiple candidate revisions Scheduling another build to catch up with Vysper Checking out Revision 0067955a578ebc103419b685453c080430b882cb (origin/nbxml-sax) > git config core.sparsecheckout # timeout=10 > git checkout -f 0067955a578ebc103419b685453c080430b882cb Commit message: "Merging in new nbxml module" First time build. Skipping changelog. Injecting SonarQube environment variables using the configuration: ASF Sonar Analysis [Vysper] $ /home/jenkins/jenkins-slave/tools/hudson.plugins.sonar.SonarRunnerInstallation/SonarQube_Scanner_2.8/bin/sonar-scanner -Dsonar.host.url=https://builds.apache.org/analysis ******** -Dsonar.projectName=VYSPER -Dsonar.projectVersion=0.8 -Dsonar.projectKey=VYSPER -Dsonar.sources=. -Dsonar.projectBaseDir=<https://builds.apache.org/job/Vysper/ws/> INFO: Scanner configuration file: /home/jenkins/jenkins-slave/tools/hudson.plugins.sonar.SonarRunnerInstallation/SonarQube_Scanner_2.8/conf/sonar-scanner.properties INFO: Project root configuration file: NONE INFO: SonarQube Scanner 2.8 INFO: Java 1.8.0_191 Oracle Corporation (64-bit) INFO: Linux 4.4.0-138-generic amd64 INFO: User cache: /home/jenkins/.sonar/cache INFO: Load global repositories INFO: Load global repositories (done) | time=1336ms INFO: Server id: 17cad23492ff68b INFO: User cache: /home/jenkins/.sonar/cache INFO: Load plugins index INFO: Load plugins index (done) | time=369ms INFO: SonarQube server 5.6.3 INFO: Default locale: "en_US", source code encoding: "ISO-8859-1" (analysis is platform dependent) INFO: Process project properties INFO: Load project repositories INFO: Load project repositories (done) | time=766ms INFO: Load quality profiles INFO: Load quality profiles (done) | time=387ms INFO: Load active rules INFO: Load active rules (done) | time=2263ms INFO: Publish mode INFO: ------------- Scan VYSPER INFO: Load server rules INFO: Load server rules (done) | time=741ms INFO: Base dir: <https://builds.apache.org/job/Vysper/ws/> INFO: Working dir: <https://builds.apache.org/job/Vysper/ws/.sonar> INFO: Source paths: . INFO: Source encoding: ISO-8859-1, default locale: en_US INFO: Index files INFO: 41 files indexed INFO: Quality profile for java: Sonar way INFO: Sensor Lines Sensor INFO: Sensor Lines Sensor (done) | time=28ms INFO: Sensor JavaSquidSensor INFO: Configured Java source version (sonar.java.source): none INFO: JavaClasspath initialization WARN: Bytecode of dependencies was not provided for analysis of source files, you might end up with less precise results. Bytecode can be provided using sonar.java.libraries property INFO: JavaClasspath initialization (done) | time=1ms INFO: JavaTestClasspath initialization INFO: JavaTestClasspath initialization (done) | time=0ms INFO: Java Main Files AST scan INFO: 41 source files to be analyzed INFO: Java Main Files AST scan (done) | time=7037ms INFO: Java Test Files AST scan INFO: 41/41 source files have been analyzed INFO: 0 source files to be analyzed INFO: Java Test Files AST scan (done) | time=1ms INFO: 0/0 source files have been analyzed INFO: Sensor JavaSquidSensor (done) | time=7913ms INFO: Sensor SCM Sensor INFO: SCM provider for this project is: git INFO: 41 files to be analyzed INFO: 41/41 files analyzed INFO: Sensor SCM Sensor (done) | time=873ms INFO: Sensor Coverage Report Import INFO: Sensor Coverage Report Import (done) | time=0ms INFO: Sensor Coverage Report Import INFO: Sensor Coverage Report Import (done) | time=0ms INFO: Sensor Unit Test Results Import INFO: Sensor Unit Test Results Import (done) | time=0ms INFO: Sensor SurefireSensor INFO: parsing <https://builds.apache.org/job/Vysper/ws/target/surefire-reports> INFO: Sensor SurefireSensor (done) | time=1ms INFO: Sensor JaCoCoSensor INFO: JaCoCoSensor: JaCoCo report not found : <https://builds.apache.org/job/Vysper/ws/target/jacoco.exec> INFO: Sensor JaCoCoSensor (done) | time=1ms INFO: Sensor JaCoCoItSensor INFO: JaCoCoItSensor: JaCoCo IT report not found: <https://builds.apache.org/job/Vysper/ws/target/jacoco-it.exec> INFO: Sensor JaCoCoItSensor (done) | time=0ms INFO: Sensor JaCoCoOverallSensor INFO: Sensor JaCoCoOverallSensor (done) | time=1ms INFO: Sensor XmlFileSensor INFO: Sensor XmlFileSensor (done) | time=0ms INFO: Sensor Zero Coverage Sensor INFO: Sensor Zero Coverage Sensor (done) | time=43ms INFO: Sensor Code Colorizer Sensor INFO: Sensor Code Colorizer Sensor (done) | time=1ms INFO: Sensor CPD Block Indexer INFO: JavaCpdBlockIndexer is used for java INFO: Sensor CPD Block Indexer (done) | time=132ms INFO: Calculating CPD for 34 files INFO: CPD calculation finished INFO: Analysis report generated in 203ms, dir size=381 KB INFO: Analysis reports compressed in 198ms, zip size=184 KB INFO: Analysis report uploaded in 759ms INFO: ANALYSIS SUCCESSFUL, you can browse https://builds.apache.org/analysis/dashboard/index/VYSPER INFO: Note that you will be able to access the updated dashboard once the server has processed the submitted analysis report INFO: More about the report processing at https://builds.apache.org/analysis/api/ce/task?id=AWyhkw_p_WT_0PKLp6EY INFO: ------------------------------------------------------------------------ INFO: EXECUTION SUCCESS INFO: ------------------------------------------------------------------------ INFO: Total time: 21.439s INFO: Final Memory: 55M/1555M INFO: ------------------------------------------------------------------------ Parsing POMs ERROR: Failed to parse POMs hudson.remoting.ProxyException: hudson.maven.MavenModuleSetBuild$MavenExecutionException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact org.apache.vysper:vysper-parent:pom:0.6-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 20, column 11 at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1391) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1125) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3086) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to H33 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at hudson.FilePath.act(FilePath.java:1072) at hudson.FilePath.act(FilePath.java:1061) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.parsePoms(MavenModuleSetBuild.java:986) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:691) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1810) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: hudson.remoting.ProxyException: org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs: [FATAL] Non-resolvable parent POM: Could not find artifact org.apache.vysper:vysper-parent:pom:0.6-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 20, column 11 at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:364) at hudson.maven.MavenEmbedder.buildProjects(MavenEmbedder.java:361) at hudson.maven.MavenEmbedder.readProjects(MavenEmbedder.java:331) at hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:1328) ... 10 more
