See
<
https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.com/job/...
Changes:
------------------------------------------
Started by upstream project
"Studio/Engineering/build_master/jbosstools-javaee-tests-matrix_master" build
number 468
originally caused by:
Started by upstream project
"Studio/Engineering/build_master/jbosstools-javaee_master" build number 454
originally caused by:
Started by upstream project
"Studio/Engineering/releng/jbosstools-pipeline_master" build number 444
originally caused by:
Started by upstream project
"Studio/Engineering/build_master/jbosstools-build.parent_master" build number
51
originally caused by:
Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on rhel7-3891 (rhel rhel7) in workspace
<
https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/S...
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
The recommended git tool is: NONE
using credential devstudio-release
Cloning the remote Git repository
Cloning repository git@github.com:jbosstools/jbosstools-javaee
Fetching upstream changes from
git@github.com:jbosstools/jbosstools-javaee
git --version # timeout=10
git --version # 'git version 1.8.3.1'
using GIT_SSH to set credentials key
used to push commits and tags via devstudio-release user to jbosstools repos
[INFO] Currently running in a labeled security context
[INFO] Currently SELinux is 'enforcing' on the host
/usr/bin/chcon --type=ssh_home_t
<
https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/S...
git fetch --tags --progress git@github.com:jbosstools/jbosstools-javaee
+refs/heads/*:refs/remotes/origin/* # timeout=10
git config remote.origin.url git@github.com:jbosstools/jbosstools-javaee # timeout=10
git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
Checking out Revision 16c44089a993f56606184faf8e19a5159c906c87 (origin/main)
git config core.sparsecheckout # timeout=10
git checkout -f 16c44089a993f56606184faf8e19a5159c906c87 # timeout=10
Commit
message: " #comment bump up to parent pom version = 4.24.0.AM1-SNAPSHOT #close"
git rev-list --no-walk 16c44089a993f56606184faf8e19a5159c906c87 #
timeout=10
[rhel7] $ Xvnc -help
Starting xvnc
[rhel7] $ Xvnc :67 -geometry 1920x1080 -rfbauth /home/hudson/.vnc/passwd
[rhel7] $ bash -xe /tmp/jenkins7728220397322821257.sh
Xvnc TigerVNC 1.8.0 - built Apr 22 2020 15:41:59
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See
http://www.tigervnc.org for information on TigerVNC.
Underlying X server release 12004000, The X.Org Foundation
Tue May 24 12:58:40 2022
vncext: VNC extension running!
vncext: Listening for VNC connections on all interface(s), port 5967
vncext: created VNC server for screen 0
++ ps ax
++ grep firefox
++ grep -v grep
+ [[ -n '' ]]
[rhel7] $ /jenkins/tools/hudson.tasks.Maven_MavenInstallation/maven3-latest/bin/mvn -f
<
https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/S...
-Djdk=openjdk-11 -DSUB=cdi/tests -DBUILD_NUMBER=454
-DUPSTREAMDEST=hudson@${HOSTNAME}:/jenkins/jbosstools-javaee_master -Dlabel=rhel7
"-DMAVEN_FLAGS=-B -U -fae -e -Dstream_jbt=master -P hudson,unified.target"
-Dmaven.test.error.ignore=true -Dmaven.test.failure.ignore=true
-DskipPrivateRequirements=true
-Dmaven.repo.local=<https://studio-jenkins-csb-codeready.apps.ocp-c1.prod.psi.redhat.comjob/Studio/job/Engineering/job/build_master/job/jbosstools-javaee-tests-matrix_master/SUB=cdi%2Ftests,jdk=openjdk-11,label=rhel7/ws/.repository>
clean verify -B -ntp -U -fae -e -P maximum,runTestsOnly -Dsurefire.timeout=10000
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to jbosstools-javaee
(${jbosstools-javaee-site}): Cannot access ${jbosstools-javaee-site} with type p2 using
the available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to jbosstools-base
(${jbosstools-base-site}): Cannot access ${jbosstools-base-site} with type p2 using the
available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to jbosstools-jst
(${jbosstools-jst-site}): Cannot access ${jbosstools-jst-site} with type p2 using the
available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to jbosstools-server
(${jbosstools-server-site}): Cannot access ${jbosstools-server-site} with type p2 using
the available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to jbosstools-hibernate
(${jbosstools-hibernate-site}): Cannot access ${jbosstools-hibernate-site} with type p2
using the available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to jbosstools-vpe
(${jbosstools-vpe-site}): Cannot access ${jbosstools-vpe-site} with type p2 using the
available connector factories: BasicRepositoryConnectorFactory
[WARNING] Could not transfer metadata
org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to
maven-default-http-blocker (
http://0.0.0.0/): transfer failed for
http://0.0.0.0/org/jboss/tools/parent/4.24.0.AM1-SNAPSHOT/maven-metadata.xml
[WARNING] org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xmlfailed to transfer
from
http://0.0.0.0/ during a previous attempt. This failure was cached in the local
repository and resolution will not be reattempted until the update interval of
maven-default-http-blocker has elapsed or updates are forced. Original error: Could not
transfer metadata org.jboss.tools:parent:4.24.0.AM1-SNAPSHOT/maven-metadata.xml from/to
maven-default-http-blocker (
http://0.0.0.0/): transfer failed for
http://0.0.0.0/org/jboss/tools/parent/4.24.0.AM1-SNAPSHOT/maven-metadata.xml
[INFO] Inspecting build with total of 13 modules...
[INFO] Installing Nexus Staging features:
[INFO] ... total of 13 executions of maven-deploy-plugin replaced with
nexus-staging-maven-plugin
[WARNING] Could not transfer metadata
org.jboss.tools.targetplatforms:jbosstools-unified:4.24.0.AM1-SNAPSHOT/maven-metadata.xml
from/to maven-default-http-blocker (
http://0.0.0.0/): transfer failed for
http://0.0.0.0/org/jboss/tools/targetplatforms/jbosstools-unified/4.24.0....
[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform
specification artifact
org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.24.0.AM1-SNAPSHOT
-> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could
not resolve target platform specification artifact
org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.24.0.AM1-SNAPSHOT
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:120)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.lang.RuntimeException: Could not resolve target platform specification
artifact
org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.24.0.AM1-SNAPSHOT
at
org.eclipse.tycho.core.resolver.DefaultTargetPlatformConfigurationReader.addTargetArtifact
(DefaultTargetPlatformConfigurationReader.java:445)
at org.eclipse.tycho.core.resolver.DefaultTargetPlatformConfigurationReader.setTarget
(DefaultTargetPlatformConfigurationReader.java:370)
at
org.eclipse.tycho.core.resolver.DefaultTargetPlatformConfigurationReader.getTargetPlatformConfiguration
(DefaultTargetPlatformConfigurationReader.java:100)
at org.eclipse.tycho.core.resolver.DefaultTychoResolver.setupProject
(DefaultTychoResolver.java:101)
at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead
(TychoMavenLifecycleParticipant.java:102)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:264)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:566)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the
following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
Build step 'Invoke top-level Maven targets' marked build as failure
Terminating xvnc.
Archiving artifacts
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files were found.
Configuration error?