![[Jenkins]](/jersey/static/18fb2cc9/images/svgs/logo.svg){kind=logo}
Started by user Dmitry Kornilov Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] node Agent default-java-n38kw is provisioned from template Kubernetes Pod Template Agent specification [Kubernetes Pod Template] (): Running on default-java-n38kw in /home/jenkins/workspace/GitHub_only_release [Pipeline] { [Pipeline] tool [Pipeline] tool [Pipeline] tool [Pipeline] sh + java -version java version "1.8.0_202" Java(TM) SE Runtime Environment (build 1.8.0_202-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode) [Pipeline] sh + mvn -version Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T18:41:47Z) Maven home: /opt/tools/apache-maven/latest Java version: 1.8.0_202, vendor: Oracle Corporation, runtime: /opt/tools/java/oracle/jdk-8/1.8.0_202/jre Default locale: en_US, platform encoding: ANSI_X3.4-1968 OS name: "linux", version: "3.10.0-957.10.1.el7.x86_64", arch: "amd64", family: "unix" [Pipeline] stage [Pipeline] { (Fetch from git) [Pipeline] git using credential f5848e71-9994-45e3-8214-137ce91ddbcf Cloning the remote Git repository Cloning repository git@github.com:eclipse-ee4j/jersey.git > git init /home/jenkins/workspace/GitHub_only_release # 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/* Checking out Revision 662158249985cf416b951418b88199f7696398d0 (refs/remotes/origin/master) > 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 > git config core.sparsecheckout # timeout=10 > git checkout -f 662158249985cf416b951418b88199f7696398d0 > git branch -a -v --no-abbrev # timeout=10 > git checkout -b master 662158249985cf416b951418b88199f7696398d0 Commit message: "remove staging repository from Travis build" > git rev-list --no-walk 662158249985cf416b951418b88199f7696398d0 # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare environment) [Pipeline] dir Running in /home/jenkins/workspace/GitHub_only_release [Pipeline] { [Pipeline] sh + grep '<version>' pom.xml + grep SNAPSHOT [Pipeline] sh + mvn -q -B '-Dexec.executable=echo' '-Dexec.args=${project.version}' --non-recursive exec:exec [Pipeline] sh + ls CONTRIBUTING.md LICENSE.md NOTICE.md README.md archetypes bom bundles connectors containers core-client core-common core-server docs etc examples ext incubator inject media pom.xml security test-framework tests tools [Pipeline] echo Current version: 2.30-SNAPSHOT [Pipeline] echo Release version: 2.29.1 [Pipeline] echo Next version: 2.30-SNAPSHOT [Pipeline] echo Release tag: 2.29.1 [Pipeline] echo Release branch: 2.29.1-BRANCH [Pipeline] echo -[ Configure git user ]-------------------------------------------------------- [Pipeline] sh + git config --local user.email jersey-bot@eclipse.org [Pipeline] sh + git config --local user.name jersey-bot [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare branch) [Pipeline] echo -[ Prepare branch ]------------------------------------------------------------- [Pipeline] echo -[ Switching to release branch ]------------------------------------------------- [Pipeline] sh + 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 <new-branch-name> HEAD is now at 66215824 remove staging repository from Travis build + true + git reset --hard origin/master HEAD is now at 66215824 remove staging repository from Travis build + true + git checkout -B 2.29.1-BRANCH Switched to a new branch '2.29.1-BRANCH' [Pipeline] echo -[ Release tag cleanup ]-------------------------------------------------------- [Pipeline] sh + git tag + grep 2.29.1 + true [Pipeline] sh + sed -i 's|<suppress files="generated" checks=".*"/>|<suppress files="generated" checks=".*"/><suppress files="unpacked-src" checks=".*"/>|g' etc/config/checkstyle-suppressions.xml [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare pom.xml for release of Jersey) [Pipeline] echo /opt/tools/java/oracle/jdk-8/latest [Pipeline] echo -[ Run maven release ]--------------------------------------------------------- [Pipeline] echo -[ Set Release version ]------------------------------------------------------- [Pipeline] sh + cd /home/jenkins/workspace/GitHub_only_release + mvn -q -B versions:set '-DnewVersion=2.29.1' '-DgenerateBackupPoms=false' + cd bom + mvn -q -B versions:set '-DnewVersion=2.29.1' '-DgenerateBackupPoms=false' + cd .. [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Prepare GitHub release) [Pipeline] sh + git checkout -- etc/config/checkstyle-suppressions.xml [Pipeline] echo -[ Perform release commit to git ]--------------------------------------------- [Pipeline] sh + git commit -a -m 2.29.1 [2.29.1-BRANCH c364e355] 2.29.1 343 files changed, 344 insertions(+), 344 deletions(-) [Pipeline] sh + git tag -m 2.29.1 -a 2.29.1 [Pipeline] echo -[ Set next snapshot version ]------------------------------------------------- [Pipeline] dir Running in /home/jenkins/workspace/GitHub_only_release [Pipeline] { [Pipeline] sh + mvn -q -B versions:set '-DnewVersion=2.30-SNAPSHOT' '-DgenerateBackupPoms=false' + cd bom + mvn -q -B versions:set '-DnewVersion=2.30-SNAPSHOT' '-DgenerateBackupPoms=false' + cd .. [Pipeline] } [Pipeline] // dir [Pipeline] echo -[ Perform commit to git ]----------------------------------------------------- [Pipeline] sh + git commit -a -m 2.30-SNAPSHOT [2.29.1-BRANCH f128b2b0] 2.30-SNAPSHOT 343 files changed, 344 insertions(+), 344 deletions(-) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Publish release to GitHub) [Pipeline] sshagent [ssh-agent] Using credentials jersey-bot (GitHub Bot SSH) [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-ZvbDtfRTnOq2/agent.703 SSH_AGENT_PID=705 Running ssh-add (command line suppressed) Identity added: /home/jenkins/workspace/GitHub_only_release@tmp/private_key_1475786887972967436.key (/home/jenkins/workspace/GitHub_only_release@tmp/private_key_1475786887972967436.key) [ssh-agent] Started. [Pipeline] { [Pipeline] sh + git push -f origin 2.29.1-BRANCH --follow-tags To github.com:eclipse-ee4j/jersey.git + e96300e3...f128b2b0 2.29.1-BRANCH -> 2.29.1-BRANCH (forced update) * [new tag] 2.29.1 -> 2.29.1 [Pipeline] } $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 705 killed; [ssh-agent] Stopped. [Pipeline] // sshagent [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline Finished: SUCCESS