Skip to content

Console Output

Started by user Dmitry Kornilov
Agent default-java-b5m6z is provisioned from template Kubernetes Pod Template
Agent specification [Kubernetes Pod Template] (): 

Building remotely on default-java-b5m6z in workspace /home/jenkins/workspace/Jersey_release
[ssh-agent] Looking for ssh-agent implementation...
[ssh-agent]   Exec ssh-agent (binary ssh-agent on a remote machine)
$ ssh-agent
SSH_AUTH_SOCK=/tmp/ssh-0IOuuGZHx8wv/agent.79
SSH_AGENT_PID=81
[ssh-agent] Started.
Running ssh-add (command line suppressed)
Identity added: /home/jenkins/workspace/Jersey_release@tmp/private_key_1176226572431958250.key (/home/jenkins/workspace/Jersey_release@tmp/private_key_1176226572431958250.key)
[ssh-agent] Using credentials jersey-bot (GitHub Bot SSH)
Cloning the remote Git repository
Cloning repository https://github.com/eclipse-ee4j/jersey
 > git init /home/jenkins/workspace/Jersey_release # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/jersey
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/eclipse-ee4j/jersey +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url https://github.com/eclipse-ee4j/jersey # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url https://github.com/eclipse-ee4j/jersey # timeout=10
Fetching upstream changes from https://github.com/eclipse-ee4j/jersey
 > git fetch --tags --progress https://github.com/eclipse-ee4j/jersey +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 0cfff66c55e31d44cc02b615e274ed9fb3a3593c (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0cfff66c55e31d44cc02b615e274ed9fb3a3593c
Commit message: "Merge pull request #3861 from agherardi/properlyClose"
 > git rev-list --no-walk 0cfff66c55e31d44cc02b615e274ed9fb3a3593c # timeout=10
provisioning config files...
copy managed file [settings-jersey.xml] to file:/home/jenkins/.m2/settings.xml
copy managed file [settings-security.xml] to file:/home/jenkins/.m2/settings-security.xml
[Jersey_release] $ /bin/sh -xe /tmp/jenkins6957789428222147533.sh
+ cat ****
+ 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
+ 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.

+ + echogpg -e --batch '5\ny\n' --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_release] $ /bin/sh -e /tmp/jenkins1969031751559761692.sh
    <version>2.28-SNAPSHOT</version>
-----BEG0B743A794876D3C78AB542A118D239B1CBCD2236
2EABB8F15F15E18885312232372703E4D5313120
Current version: 2.28-SNAPSHOT
Release version: 2.28
Next version:    2.29-SNAPSHOT
Release tag:     2.28-RELEASE
-[ Dry run turned on ]----------------------------------------------------------
-[ Prepare branch ]-------------------------------------------------------------
-[ Swiching to release branch ]-------------------------------------------------
Previous HEAD position was 0cfff66 Merge pull request #3861 from agherardi/properlyClose
Branch 'EE4J_8' set up to track remote branch 'EE4J_8' from 'origin'.
Switched to a new branch 'EE4J_8'
HEAD is now at 7aebbcf Uptake Jakarta dependencies, Part I. (#4001)
error: branch '2.28' not found.
Switched to a new branch '2.28'
-[ Release tag cleanup ]--------------------------------------------------------
error: tag '2.28-RELEASE' not found.
java version "1.8.0_181"
Java(TM) SE Runtime Environment (build 1.8.0_181-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z)
Maven home: /opt/tools/apache-maven/latest
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime: /opt/tools/java/oracle/jdk-8/1.8.0_181/jre
Default locale: en_US, platform encoding: ANSI_X3.4-1968
OS name: "linux", version: "3.10.0-957.1.3.el7.x86_64", arch: "amd64", family: "unix"
/opt/tools/java/oracle/jdk-8/latest
-[ Run maven release ]---------------------------------------------------------
-[ Set Release version ]-------------------------------------------------------
[INFO] Scanning for projects...
Downloading from eclipse.maven.central.mirror: https://repo.eclipse.org/content/repositories/maven_central/org/eclipse/ee4j/project/1.0.5/project-1.0.5.pom
Progress (1): 4.1/13 kB
Progress (1): 7.7/13 kB
Progress (1): 12/13 kB 
Progress (1): 13 kB   
                   
Downloaded from eclipse.maven.central.mirror: https://repo.eclipse.org/content/repositories/maven_central/org/eclipse/ee4j/project/1.0.5/project-1.0.5.pom (13 kB at 2.5 kB/s)
Downloading from eclipse.maven.central.mirror: https://repo.eclipse.org/content/repositories/maven_central/org/glassfish/hk2/hk2-bom/2.5.0/hk2-bom-2.5.0.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Could not find artifact org.glassfish.hk2:hk2-bom:pom:2.5.0 in eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/) @ line 1391, column 25
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project org.glassfish.jersey:project:2.28-SNAPSHOT (/home/jenkins/workspace/Jersey_release/pom.xml) has 1 error
[ERROR]     Non-resolvable import POM: Could not find artifact org.glassfish.hk2:hk2-bom:pom:2.5.0 in eclipse.maven.central.mirror (https://repo.eclipse.org/content/repositories/maven_central/) @ line 1391, column 25 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
Build step 'Execute shell' marked build as failure
$ ssh-agent -k
unset SSH_AUTH_SOCK;
unset SSH_AGENT_PID;
echo Agent pid 81 killed;
[ssh-agent] Stopped.
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE