Started by user Dmitry Kornilov Running in Durability level: MAX_SURVIVABILITY [Pipeline] node Still waiting to schedule task Waiting for next available executor Agent default-java-hb02d is provisioned from template Kubernetes Pod Template Agent specification [Kubernetes Pod Template] (): Running on default-java-hb02d in /home/jenkins/workspace/Jersey_release_pipeline_II [Pipeline] { [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + /opt/tools/java/oracle/jdk-8/1.8.0_181/bin/java -version 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) [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + java -version 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) [Pipeline] stage [Pipeline] { (Fetch from git) [Pipeline] git Cloning the remote Git repository Cloning repository git@github.com:eclipse-ee4j/jersey.git > git init /home/jenkins/workspace/Jersey_release_pipeline_II # timeout=10 Fetching upstream changes from git@github.com:eclipse-ee4j/jersey.git > git --version # timeout=10 using GIT_SSH to set credentials GitHub Bot SSH > git fetch --tags --progress git@github.com:eclipse-ee4j/jersey.git +refs/heads/*:refs/remotes/origin/* > 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 > git config remote.origin.url git@github.com:eclipse-ee4j/jersey.git # timeout=10 Fetching upstream changes from git@github.com:eclipse-ee4j/jersey.git using GIT_SSH to set credentials GitHub Bot SSH > git fetch --tags --progress git@github.com:eclipse-ee4j/jersey.git +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 e4c209877f6bd1b29dbd03e2fabc765dc0b34ff9 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f e4c209877f6bd1b29dbd03e2fabc765dc0b34ff9 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master e4c209877f6bd1b29dbd03e2fabc765dc0b34ff9 Commit message: "Merge pull request #3958 from eclipse-ee4j/arjantijms-patch-1" First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare environment) [Pipeline] dir Running in /home/jenkins/workspace/Jersey_release_pipeline_II [Pipeline] { [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + grep '' pom.xml + grep SNAPSHOT [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + /opt/tools/apache-maven/latest/bin/mvn -B org.apache.maven.plugins:maven-help-plugin:2.1.1:evaluate '-Dexpression=project.version' + grep -E '^[0-9]+(.[0-9]+)+-SNAPSHOT$' [Pipeline] echo Current version: 2.28-SNAPSHOT [Pipeline] echo Release version: 2.28 [Pipeline] echo Next version: 2.29-SNAPSHOT [Pipeline] echo Release tag: 2.28-RELEASE [Pipeline] echo -[ Dry run turned on ]---------------------------------------------------------- [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare GPG) [Pipeline] withCredentials [Pipeline] { [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + 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 " 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 [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + gpg --list-keys --with-colons + awk -F: '/fpr:/ {print $10}' + sort -u + echo -e '5 y ' + 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 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 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 Please note that the shown key validity is not necessarily correct unless you restart the program. + gpg+ --batch --command-fdecho 0 --expert -e --edit-key '5 y ' 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 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 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 [Pipeline] } [Pipeline] // withCredentials [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare branch) [Pipeline] echo -[ Prepare branch ]------------------------------------------------------------- [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + git branch -r [Pipeline] echo -[ Swiching to release branch ]------------------------------------------------- [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + git checkout origin/master Note: checking out 'origin/master'. You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make in this state without impacting any branches by performing another checkout. If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again. Example: git checkout -b HEAD is now at e4c2098 Merge pull request #3958 from eclipse-ee4j/arjantijms-patch-1 + true + git reset --hard origin/master HEAD is now at e4c2098 Merge pull request #3958 from eclipse-ee4j/arjantijms-patch-1 + true + git branch --delete 2.28 error: branch '2.28' not found. + git checkout -b 2.28 Switched to a new branch '2.28' [Pipeline] echo -[ Release tag cleanup ]-------------------------------------------------------- [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + git tag [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Build JSTL-API) [Pipeline] echo /opt/tools/java/oracle/jdk-8/1.8.0_181 [Pipeline] echo -[ Run maven release ]--------------------------------------------------------- [Pipeline] echo -[ Set Release version ]------------------------------------------------------- [Pipeline] sh [Jersey_release_pipeline_II] Running shell script + cd . + /opt/tools/apache-maven/latest/bin/mvn -q versions:set '-DnewVersion=2.28' + /opt/tools/apache-maven/latest/bin/mvn -q versions:commit [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] Non-resolvable import POM: Could not find artifact org.glassfish.jersey:jersey-bom:pom:2.28 in central (https://repo.maven.apache.org/maven2) @ org.glassfish.jersey.tests:project:[unknown-version], /home/jenkins/workspace/Jersey_release_pipeline_II/tests/pom.xml, line 56, column 25 [ERROR] Non-resolvable import POM: Failure to find org.glassfish.jersey:jersey-bom:pom:2.28 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.glassfish.jersey.examples:project:[unknown-version], /home/jenkins/workspace/Jersey_release_pipeline_II/examples/pom.xml, line 131, column 25 [WARNING] The expression ${artifactId} is deprecated. Please use ${project.artifactId} instead. @ [WARNING] The expression ${artifactId} is deprecated. Please use ${project.artifactId} instead. @ @ [ERROR] The build could not read 2 projects -> [Help 1] [ERROR] [ERROR] The project org.glassfish.jersey.tests:project:2.28 (/home/jenkins/workspace/Jersey_release_pipeline_II/tests/pom.xml) has 1 error [ERROR] Non-resolvable import POM: Could not find artifact org.glassfish.jersey:jersey-bom:pom:2.28 in central (https://repo.maven.apache.org/maven2) @ org.glassfish.jersey.tests:project:[unknown-version], /home/jenkins/workspace/Jersey_release_pipeline_II/tests/pom.xml, line 56, column 25 -> [Help 2] [ERROR] [ERROR] The project org.glassfish.jersey.examples:project:2.28 (/home/jenkins/workspace/Jersey_release_pipeline_II/examples/pom.xml) has 1 error [ERROR] Non-resolvable import POM: Failure to find org.glassfish.jersey:jersey-bom:pom:2.28 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced @ org.glassfish.jersey.examples:project:[unknown-version], /home/jenkins/workspace/Jersey_release_pipeline_II/examples/pom.xml, line 131, 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 [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE