Skip to content
Failed

Console Output

Started by user Maxim Nesen
Rebuilds build #48
Running as Maxim Nesen
Agent basic-srlqs is provisioned from template basic
---
apiVersion: "v1"
kind: "Pod"
metadata:
  annotations: {}
  labels:
    jenkins: "slave"
    jenkins/label-digest: "61a7508ed1b04e9ada836fcd14d4d8ef5687c7dd"
    jenkins/label: "basic"
  name: "basic-srlqs"
  namespace: "jersey"
spec:
  containers:
  - env:
    - name: "JENKINS_SECRET"
      value: "********"
    - name: "JENKINS_TUNNEL"
      value: "jenkins-discovery.jersey.svc.cluster.local:50000"
    - name: "JENKINS_AGENT_NAME"
      value: "basic-srlqs"
    - name: "JENKINS_REMOTING_JAVA_OPTS"
      value: "-showversion -XshowSettings:vm -Xmx256m -Dorg.jenkinsci.remoting.engine.JnlpProtocol3.disabled=true\
        \ -Dorg.jenkinsci.plugins.gitclient.CliGitAPIImpl.useSETSID=true"
    - name: "JAVA_TOOL_OPTIONS"
      value: ""
    - name: "_JAVA_OPTIONS"
      value: ""
    - name: "OPENJ9_JAVA_OPTIONS"
      value: "-XX:+IgnoreUnrecognizedVMOptions -XX:+IdleTuningCompactOnIdle -XX:+IdleTuningGcOnIdle"
    - name: "JENKINS_NAME"
      value: "basic-srlqs"
    - name: "JENKINS_AGENT_WORKDIR"
      value: "/home/jenkins/agent"
    - name: "JENKINS_URL"
      value: "http://jenkins-ui.jersey.svc.cluster.local/jersey/"
    image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-3044.vb_940a_a_e4f72e"
    imagePullPolicy: "Always"
    name: "jnlp"
    resources:
      limits:
        cpu: "2000m"
        memory: "4096Mi"
      requests:
        cpu: "1000m"
        memory: "4096Mi"
    tty: true
    volumeMounts:
    - mountPath: "/home/jenkins/.m2/toolchains.xml"
      name: "m2-dir"
      readOnly: true
      subPath: "toolchains.xml"
    - mountPath: "/home/jenkins/.mavenrc"
      name: "m2-dir"
      readOnly: true
      subPath: ".mavenrc"
    - mountPath: "/opt/tools"
      name: "volume-0"
      readOnly: false
    - mountPath: "/home/jenkins"
      name: "volume-2"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/repository"
      name: "volume-3"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/settings-security.xml"
      name: "m2-secret-dir"
      readOnly: true
      subPath: "settings-security.xml"
    - mountPath: "/home/jenkins/.m2/wrapper"
      name: "volume-4"
      readOnly: false
    - mountPath: "/home/jenkins/.m2/settings.xml"
      name: "m2-secret-dir"
      readOnly: true
      subPath: "settings.xml"
    - mountPath: "/home/jenkins/.ssh"
      name: "volume-1"
      readOnly: false
      subPath: ""
    - mountPath: "/home/jenkins/agent"
      name: "workspace-volume"
      readOnly: false
    workingDir: "/home/jenkins/agent"
  nodeSelector:
    kubernetes.io/os: "linux"
  restartPolicy: "Never"
  volumes:
  - name: "volume-0"
    persistentVolumeClaim:
      claimName: "tools-claim-jiro-jersey"
      readOnly: true
  - name: "m2-secret-dir"
    secret:
      secretName: "m2-secret-dir"
  - emptyDir:
      medium: ""
    name: "volume-2"
  - configMap:
      name: "m2-dir"
    name: "m2-dir"
  - configMap:
      name: "known-hosts"
    name: "volume-1"
  - emptyDir:
      medium: ""
    name: "workspace-volume"
  - emptyDir:
      medium: ""
    name: "volume-4"
  - emptyDir:
      medium: ""
    name: "volume-3"

Building remotely on basic-srlqs (basic) in workspace /home/jenkins/agent/workspace/Jersey-apidocs_bundle_release
The recommended git tool is: git
using credential github-bot-ssh
Cloning the remote Git repository
Cloning repository git@github.com:eclipse-ee4j/jersey.git
 > git init /home/jenkins/agent/workspace/Jersey-apidocs_bundle_release # timeout=10
Fetching upstream changes from git@github.com:eclipse-ee4j/jersey.git
 > git --version # timeout=10
 > git --version # 'git version 2.20.1'
using GIT_SSH to set credentials GitHub bot SSH
[INFO] Currently running in a labeled security context
 > /usr/bin/chcon --type=ssh_home_t /home/jenkins/agent/workspace/Jersey-apidocs_bundle_release@tmp/jenkins-gitclient-ssh15557455329590260584.key
Verifying host key using known hosts file
 > git fetch --tags --force --progress -- git@github.com:eclipse-ee4j/jersey.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git@github.com:eclipse-ee4j/jersey.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
Avoid second fetch
 > git rev-parse refs/remotes/origin/tags/2.39^{commit} # timeout=10
 > git rev-parse tags/2.39^{commit} # timeout=10
Checking out Revision a40074eef3c79cfc466feb37d525b0101539780a (tags/2.39)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f a40074eef3c79cfc466feb37d525b0101539780a # timeout=10
Commit message: "2.39"
First time build. Skipping changelog.
[Jersey-apidocs_bundle_release] $ /bin/sh -xe /tmp/jenkins13386754835620090127.sh
+ gpg --batch --import ****
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: key 372703E4D5313120: 1 signature not checked due to a missing key
gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created
gpg: key 372703E4D5313120: public key "Eclipse Jersey <jersey-dev@eclipse.org>" imported
gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status
gpg: key 372703E4D5313120: secret key imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg:       secret keys read: 1
gpg:   secret keys imported: 1
gpg: no ultimately trusted keys found
++ gpg --list-keys --with-colons
++ awk -F: '/fpr:/ {print $10}'
++ sort -u
+ for fpr in $(gpg --list-keys --with-colons  | awk -F: '/fpr:/ {print $10}' | sort -u)
+ echo -e '5\ny\n'
+ gpg --batch --command-fd 0 --expert --edit-key 0B743A794876D3C78AB542A118D239B1CBCD2236 trust
Secret subkeys are available.

pub  rsa4096/372703E4D5313120
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: unknown       validity: unknown
ssb  rsa4096/18D239B1CBCD2236
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Jersey <jersey-dev@eclipse.org>

pub  rsa4096/372703E4D5313120
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: unknown       validity: unknown
ssb  rsa4096/18D239B1CBCD2236
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Jersey <jersey-dev@eclipse.org>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu


pub  rsa4096/372703E4D5313120
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: unknown
ssb  rsa4096/18D239B1CBCD2236
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Jersey <jersey-dev@eclipse.org>
Please note that the shown key validity is not necessarily correct
unless you restart the program.

+ for fpr in $(gpg --list-keys --with-colons  | awk -F: '/fpr:/ {print $10}' | sort -u)
+ echo -e '5\ny\n'
+ gpg --batch --command-fd 0 --expert --edit-key 2EABB8F15F15E18885312232372703E4D5313120 trust
Secret subkeys are available.

gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2023-10-02
pub  rsa4096/372703E4D5313120
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/18D239B1CBCD2236
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Jersey <jersey-dev@eclipse.org>

pub  rsa4096/372703E4D5313120
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/18D239B1CBCD2236
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Jersey <jersey-dev@eclipse.org>

Please decide how far you trust this user to correctly verify other users' keys
(by looking at passports, checking fingerprints from different sources, etc.)

  1 = I don't know or won't say
  2 = I do NOT trust
  3 = I trust marginally
  4 = I trust fully
  5 = I trust ultimately
  m = back to the main menu


pub  rsa4096/372703E4D5313120
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/18D239B1CBCD2236
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Jersey <jersey-dev@eclipse.org>

[Jersey-apidocs_bundle_release] $ /bin/bash -xe /tmp/jenkins11416821044881650233.sh
+ MVN_HOME=/opt/tools/apache-maven/latest/
+ PATH=/opt/tools/apache-maven/latest//bin:/opt/tools/java/oracle/jdk-8/latest:/bin:/opt/tools/java/oracle/jdk-8/latest/bin:/opt/tools/java/oracle/jdk-8/latest/bin:/opt/java/openjdk/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ [[ 2.39 == 2* ]]
+ export PROFILE_BUNDLE=,jetty2x
+ PROFILE_BUNDLE=,jetty2x
+ echo '-[ Run maven release plugin ]---------------------------------------------------'
-[ Run maven release plugin ]---------------------------------------------------
+ mvn -q -C -DstagingDescription=org.glassfish.jersey.bundles.apidocs:2.39 -Pstaging,oss-release,pre-release,jetty2x -DskipTests -Denforcer.skip -pl bundles/apidocs install javadoc:jar gpg:sign deploy
[ERROR] Failed to execute goal on project apidocs: Could not resolve dependencies for project org.glassfish.jersey.bundles:apidocs:jar:2.39: The following artifacts could not be resolved: org.glassfish.jersey.core:jersey-server:jar:2.39, org.glassfish.jersey.core:jersey-client:jar:2.39, org.glassfish.jersey.core:jersey-common:jar:2.39, org.glassfish.jersey.connectors:jersey-apache-connector:jar:2.39, org.glassfish.jersey.connectors:jersey-apache5-connector:jar:2.39, org.glassfish.jersey.connectors:jersey-grizzly-connector:jar:2.39, org.glassfish.jersey.connectors:jersey-helidon-connector:jar:2.39, org.glassfish.jersey.connectors:jersey-jdk-connector:jar:2.39, org.glassfish.jersey.connectors:jersey-jetty-connector:jar:2.39, org.glassfish.jersey.connectors:jersey-netty-connector:jar:2.39, org.glassfish.jersey.containers:jersey-container-servlet:jar:2.39, org.glassfish.jersey.containers:jersey-container-servlet-core:jar:2.39, org.glassfish.jersey.containers:jersey-container-simple-http:jar:2.39, org.glassfish.jersey.containers:jersey-container-jdk-http:jar:2.39, org.glassfish.jersey.containers:jersey-container-grizzly2-http:jar:2.39, org.glassfish.jersey.containers:jersey-container-grizzly2-servlet:jar:2.39, org.glassfish.jersey.media:jersey-media-jaxb:jar:2.39, org.glassfish.jersey.media:jersey-media-json-binding:jar:2.39, org.glassfish.jersey.media:jersey-media-json-jackson:jar:2.39, org.glassfish.jersey.media:jersey-media-json-jettison:jar:2.39, org.glassfish.jersey.media:jersey-media-json-processing:jar:2.39, org.glassfish.jersey.media:jersey-media-moxy:jar:2.39, org.glassfish.jersey.media:jersey-media-multipart:jar:2.39, org.glassfish.jersey.media:jersey-media-sse:jar:2.39, org.glassfish.jersey.media:jersey-media-kryo:jar:2.39, org.glassfish.jersey.inject:jersey-cdi2-se:jar:2.39, org.glassfish.jersey.inject:jersey-hk2:jar:2.39, org.glassfish.jersey.ext.cdi:jersey-cdi1x:jar:2.39, org.glassfish.jersey.ext:jersey-declarative-linking:jar:2.39, org.glassfish.jersey.ext.microprofile:jersey-mp-config:jar:2.39, org.glassfish.jersey.ext.microprofile:jersey-mp-rest-client:jar:2.39, org.glassfish.jersey.ext:jersey-wadl-doclet:jar:2.39, org.glassfish.jersey.incubator:jersey-open-tracing:jar:2.39, org.glassfish.jersey.security:oauth1-signature:jar:2.39, org.glassfish.jersey.media:jersey-media-json-jackson1:jar:2.39: Could not find artifact org.glassfish.jersey.core:jersey-server:jar:2.39 in sonatype-nexus-staging (https://jakarta.oss.sonatype.org/content/repositories/staging/) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[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/DependencyResolutionException
Build step 'Execute shell' marked build as failure
Finished: FAILURE