Skip to content
Failed

Console Output

Started by user Dmitry Kornilov
Running as Dmitry Kornilov
Agent basic-l6wjt is provisioned from template basic
---
apiVersion: "v1"
kind: "Pod"
metadata:
  annotations: {}
  labels:
    jenkins: "slave"
    jenkins/label: ""
  name: "basic-l6wjt"
spec:
  containers:
  - env:
    - name: "JENKINS_SECRET"
      value: "********"
    - name: "JENKINS_TUNNEL"
      value: "jenkins-discovery.jaf.svc.cluster.local:50000"
    - name: "JENKINS_AGENT_NAME"
      value: "basic-l6wjt"
    - 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-l6wjt"
    - name: "JENKINS_AGENT_WORKDIR"
      value: "/home/jenkins/agent"
    - name: "JENKINS_URL"
      value: "http://jenkins-ui.jaf.svc.cluster.local/jaf/"
    image: "docker.io/eclipsecbi/jiro-agent-basic:remoting-4.5"
    imagePullPolicy: "Always"
    name: "jnlp"
    resources:
      limits:
        memory: "4096Mi"
        cpu: "2000m"
      requests:
        memory: "4096Mi"
        cpu: "1000m"
    securityContext:
      privileged: false
    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
    - mountPath: "/home/jenkins/agent"
      name: "workspace-volume"
      readOnly: false
    workingDir: "/home/jenkins/agent"
  nodeSelector:
    beta.kubernetes.io/os: "linux"
  restartPolicy: "Never"
  securityContext: {}
  volumes:
  - name: "volume-0"
    persistentVolumeClaim:
      claimName: "tools-claim-jiro-jaf"
      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-l6wjt in workspace /home/jenkins/agent/workspace/activation-build-stage
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
The recommended git tool is: NONE
using credential github-bot-ssh
Cloning the remote Git repository
Cloning repository git@github.com:eclipse-ee4j/jaf.git
 > git init /home/jenkins/agent/workspace/activation-build-stage # timeout=10
Fetching upstream changes from git@github.com:eclipse-ee4j/jaf.git
 > git --version # timeout=10
 > git --version # 'git version 2.26.2'
using GIT_SSH to set credentials GitHub bot SSH
 > git fetch --tags --force --progress -- git@github.com:eclipse-ee4j/jaf.git +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git@github.com:eclipse-ee4j/jaf.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/master^{commit} # timeout=10
Checking out Revision c2c887b5db31d479a06ef429dcf202a139dad6ab (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c2c887b5db31d479a06ef429dcf202a139dad6ab # timeout=10
 > git branch -a -v --no-abbrev # timeout=10
 > git checkout -b master c2c887b5db31d479a06ef429dcf202a139dad6ab # timeout=10
Commit message: "JUnit dependency and maven-surefire-plugin removal from POMs Because there are no any unit/integration tests in the project JUnit dependency and maven-surefire-plugin these components are not needed in POM files."
First time build. Skipping changelog.
[activation-build-stage] $ /bin/bash -ex /tmp/jenkins6453714645043093847.sh
+ TOOLS_PREFIX=/opt/tools
+ JAVA_PREFIX=/opt/tools/java/openjdk
+ MVN_HOME=/opt/tools/apache-maven/latest
+ JAVA_HOME=/opt/tools/java/openjdk/jdk-11/latest
+ PATH=/opt/tools/apache-maven/latest/bin:/opt/tools/java/openjdk/jdk-11/latest/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ VERSIONS_PLUGIN=org.codehaus.mojo:versions-maven-plugin:2.7
+ HELP_PLUGIN=org.apache.maven.plugins:maven-help-plugin:3.1.0
+ grep '<version>' pom.xml
+ grep SNAPSHOT
    <version>2.0.1-SNAPSHOT</version>
++ mvn -B org.apache.maven.plugins:maven-help-plugin:3.1.0:evaluate -Dexpression=project.version
++ grep -E '^[0-9]+(\.[0-9]+)+-SNAPSHOT$'
+ SNAPSHOT_VERSION=2.0.1-SNAPSHOT
+ '[' -z 2.0.1 ']'
+ '[' -z 2.0.1-SNAPSHOT ']'
+ RELEASE_TAG=2.0.1
+ RELEASE_BRANCH=2.0.1-RELEASE
+ echo 'Current version: 2.0.1-SNAPSHOT'
Current version: 2.0.1-SNAPSHOT
+ echo 'Release version: 2.0.1'
Release version: 2.0.1
+ echo 'Next version:    2.0.1-SNAPSHOT'
Next version:    2.0.1-SNAPSHOT
+ echo 'Release branch:  2.0.1-RELEASE'
Release branch:  2.0.1-RELEASE
+ echo 'Release tag:     2.0.1'
Release tag:     2.0.1
+ '[' -z 2.0.1-SNAPSHOT -o -z 2.0.1 -o -z 2.0.1-SNAPSHOT ']'
+ '[' false = true ']'
+ MVN_DEPLOY_ARGS=deploy
++ git remote
+ GIT_ORIGIN=origin
+ echo '-[ Prepare branch ]-------------------------------------------------------------'
-[ Prepare branch ]-------------------------------------------------------------
++ git branch -r
++ grep origin/2.0.1-RELEASE
+ [[ -n '' ]]
+ echo '-[ Release tag cleanup ]--------------------------------------------------------'
-[ Release tag cleanup ]--------------------------------------------------------
++ git tag
++ grep 2.0.1
+ '[' -n ']'
+ '[' true = true ']'
+ echo '2.0.1 tag already exists, deleting'
2.0.1 tag already exists, deleting
+ git push --delete origin 2.0.1
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
+ cd /home/jenkins/agent/workspace/activation-build-stage
+ git branch --delete 2.0.1-RELEASE
error: branch '2.0.1-RELEASE' not found.
+ git checkout -b 2.0.1-RELEASE
Switched to a new branch '2.0.1-RELEASE'
+ git tag --delete 2.0.1
error: tag '2.0.1' not found.
+ git config --global user.email jaf-bot@eclipse.org
+ git config --global user.name 'Eclipse JAF Bot'
+ gpg --batch --import ****
gpg: directory '/home/jenkins/.gnupg' created
gpg: keybox '/home/jenkins/.gnupg/pubring.kbx' created
gpg: key 3A1959EEF8726006: 1 signature not checked due to a missing key
gpg: /home/jenkins/.gnupg/trustdb.gpg: trustdb created
gpg: key 3A1959EEF8726006: public key "Eclipse Project for JAF <jaf-dev@eclipse.org>" imported
gpg: To migrate 'secring.gpg', with each smartcard, run: gpg --card-status
gpg: key 3A1959EEF8726006: 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 6DD3B8C64EF75253BEB2C53AD908A43FB7EC07AC trust
Secret subkeys are available.

pub  rsa4096/3A1959EEF8726006
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: unknown       validity: unknown
ssb  rsa4096/D908A43FB7EC07AC
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Project for JAF <jaf-dev@eclipse.org>

pub  rsa4096/3A1959EEF8726006
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: unknown       validity: unknown
ssb  rsa4096/D908A43FB7EC07AC
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Project for JAF <jaf-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/3A1959EEF8726006
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: unknown
ssb  rsa4096/D908A43FB7EC07AC
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ unknown] (1). Eclipse Project for JAF <jaf-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 CAE38BC93D90B852D88465DD3A1959EEF8726006 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/3A1959EEF8726006
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/D908A43FB7EC07AC
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Project for JAF <jaf-dev@eclipse.org>

pub  rsa4096/3A1959EEF8726006
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/D908A43FB7EC07AC
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Project for JAF <jaf-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/3A1959EEF8726006
     created: 2018-10-03  expires: 2023-10-02  usage: SCEA
     trust: ultimate      validity: ultimate
ssb  rsa4096/D908A43FB7EC07AC
     created: 2018-10-03  expires: 2023-10-02  usage: S   
[ultimate] (1). Eclipse Project for JAF <jaf-dev@eclipse.org>

+ cd
++ mvn -B org.apache.maven.plugins:maven-help-plugin:3.1.0:evaluate -Dexpression=project.artifactId
++ grep -Ev '(^\[)'
+ ARTIFACT_ID=standalone-pom
++ mvn -B org.apache.maven.plugins:maven-help-plugin:3.1.0:evaluate -Dexpression=project.groupId
++ grep -Ev '(^\[)'
+ GROUP_ID=org.apache.maven
+ STAGING_DESC=org.apache.maven:standalone-pom:2.0.1
++ echo org.apache.maven:standalone-pom:2.0.1
++ sed -e 's/\./\\\./g'
+ STAGING_KEY='org\.apache\.maven:standalone-pom:2\.0\.1'
+ echo '-[ Set release version ]--------------------------------------------------------'
-[ Set release version ]--------------------------------------------------------
+ mvn -U -C -B -DnewVersion=2.0.1 -DgenerateBackupPoms=false clean org.codehaus.mojo:versions-maven-plugin:2.7:set
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.095 s
[INFO] Finished at: 2021-02-12T08:11:03Z
[INFO] ------------------------------------------------------------------------
[ERROR] The goal you specified requires a project to execute but there is no POM in this directory (/home/jenkins). Please verify you invoked Maven from the correct directory. -> [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/MissingProjectException
Build step 'Execute shell' marked build as failure
Finished: FAILURE