06:46:21 Démarré par le projet amont "Silverpeas_Stable_AutoDeploy" de numéro de build 550 06:46:21 Causé à l'origine par : 06:46:21 Lancé par une alarme périodique 06:46:21 Running as userbuild 06:46:21 Obtained src/builds/mobile/Jenkinsfile from git https://github.com/Silverpeas/Jenkins-Pipelines.git 06:46:21 [Pipeline] Start of Pipeline 06:46:22 [Pipeline] node 06:46:22 Running on Jenkins in /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy 06:46:22 [Pipeline] { 06:46:22 [Pipeline] stage 06:46:22 [Pipeline] { (Declarative: Checkout SCM) 06:46:22 [Pipeline] checkout 06:46:22 Selected Git installation does not exist. Using Default 06:46:22 The recommended git tool is: NONE 06:46:22 No credentials specified 06:46:22 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy/.git # timeout=10 06:46:22 Fetching changes from the remote Git repository 06:46:22 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/Jenkins-Pipelines.git # timeout=10 06:46:22 Cleaning workspace 06:46:22 > /usr/bin/git rev-parse --verify HEAD # timeout=10 06:46:22 Resetting working tree 06:46:22 > /usr/bin/git reset --hard # timeout=10 06:46:22 > /usr/bin/git clean -fdx # timeout=10 06:46:22 Fetching upstream changes from https://github.com/Silverpeas/Jenkins-Pipelines.git 06:46:22 > /usr/bin/git --version # timeout=10 06:46:22 > git --version # 'git version 2.43.0' 06:46:22 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/Jenkins-Pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 06:46:24 > /usr/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10 06:46:24 Checking out Revision 01016743dfe6029fbec83eb133b58304d428f058 (refs/remotes/origin/master) 06:46:24 > /usr/bin/git config core.sparsecheckout # timeout=10 06:46:24 > /usr/bin/git checkout -f 01016743dfe6029fbec83eb133b58304d428f058 # timeout=10 06:46:24 Commit message: "Update the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)" 06:46:24 > /usr/bin/git rev-list --no-walk ee417f2e12a50c898fce7d66542b733c63b400a8 # timeout=10 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] withEnv 06:46:24 [Pipeline] { 06:46:24 [Pipeline] isUnix 06:46:24 [Pipeline] withEnv 06:46:24 [Pipeline] { 06:46:24 [Pipeline] sh 06:46:24 + docker inspect -f . silverpeas/silverbuild:6.4 06:46:24 . 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // withEnv 06:46:24 [Pipeline] withDockerContainer 06:46:24 Jenkins does not seem to be running inside a container 06:46:24 $ docker run -t -d -u 111:119 -v $HOME/.m2/settings.xml:/home/silverbuild/.m2/settings.xml -v $HOME/.m2/settings-security.xml:/home/silverbuild/.m2/settings-security.xml -v $HOME/.gitconfig:/home/silverbuild/.gitconfig -v $HOME/.ssh:/home/silverbuild/.ssh -v $HOME/.gnupg:/home/silverbuild/.gnupg -w /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy -v /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy:/var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy:rw,z -v /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy@tmp:/var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** silverpeas/silverbuild:6.4 cat 06:46:25 $ docker top 4ed70fb4451876b2c8eaeeff2d755c1328dc98b234de51165ca27531a9f52e1e -eo pid,comm 06:46:25 [Pipeline] { 06:46:25 [Pipeline] withEnv 06:46:25 [Pipeline] { 06:46:25 [Pipeline] stage 06:46:25 [Pipeline] { (Resolve dependency on Silverpeas) 06:46:25 [Pipeline] script 06:46:25 [Pipeline] { 06:46:25 [Pipeline] echo 06:46:25 Working on branch 6.4.x 06:46:25 [Pipeline] copyArtifacts 06:46:25 Copied 1 artifact from "Silverpeas_Stable_AutoDeploy" build number 550 06:46:25 [Pipeline] readYaml 06:46:25 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named parentVersion (to a value of type String) which could lead to memory leaks or other issues. 06:46:25 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named silverpeasVersion (to a value of type String) which could lead to memory leaks or other issues. 06:46:25 [Pipeline] sh 06:46:25 + rm -f build.yaml 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // script 06:46:25 [Pipeline] echo 06:46:25 Parent version is 1.6.3 06:46:25 [Pipeline] echo 06:46:25 Silverpeas version is 6.4.8-build260720 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // stage 06:46:25 [Pipeline] stage 06:46:25 [Pipeline] { (Prepare the project) 06:46:25 [Pipeline] git 06:46:25 The recommended git tool is: /usr/bin/git 06:46:25 using credential cacc0467-7c85-41d1-bf4e-eaa470dd5e59 06:46:25 Warning: JENKINS-30600: special launcher org.jenkinsci.plugins.docker.workflow.WithContainerStep$Decorator$1@70f6abf5; decorates hudson.Launcher$LocalLauncher@6fc8b079 will be ignored (a typical symptom is the Git executable not being run inside a designated container) 06:46:25 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy/.git # timeout=10 06:46:25 Fetching changes from the remote Git repository 06:46:25 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/silverpeasmobile # timeout=10 06:46:25 Fetching upstream changes from https://github.com/Silverpeas/silverpeasmobile 06:46:25 > /usr/bin/git --version # timeout=10 06:46:25 > git --version # 'git version 2.43.0' 06:46:25 using GIT_ASKPASS to set credentials GitHub Credentials For Jenkins 06:46:25 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/silverpeasmobile +refs/heads/*:refs/remotes/origin/* # timeout=10 06:46:26 > /usr/bin/git rev-parse refs/remotes/origin/6.4.x^{commit} # timeout=10 06:46:26 Checking out Revision d61323d6543c581b320ce7972f169f04dd165eba (refs/remotes/origin/6.4.x) 06:46:26 > /usr/bin/git config core.sparsecheckout # timeout=10 06:46:26 > /usr/bin/git checkout -f d61323d6543c581b320ce7972f169f04dd165eba # timeout=10 06:46:27 > /usr/bin/git branch -a -v --no-abbrev # timeout=10 06:46:27 > /usr/bin/git branch -D 6.4.x # timeout=10 06:46:27 > /usr/bin/git checkout -b 6.4.x d61323d6543c581b320ce7972f169f04dd165eba # timeout=10 06:46:27 Commit message: "Update dependency on Silverpeas to version 6.4.8-build260720" 06:46:27 > /usr/bin/git rev-list --no-walk d61323d6543c581b320ce7972f169f04dd165eba # timeout=10 06:46:27 [Pipeline] script 06:46:27 [Pipeline] { 06:46:27 [Pipeline] copyArtifacts 06:46:27 Copied 1 artifact from "Silverpeas_Mobile_Stable_AutoDeploy" build number 420 06:46:27 [Pipeline] readYaml 06:46:27 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named previousBuildVersion (to a value of type String) which could lead to memory leaks or other issues. 06:46:27 [Pipeline] sh 06:46:27 + git rev-parse HEAD 06:46:27 [Pipeline] echo 06:46:27 Current commit is d61323d6543c581b320ce7972f169f04dd165eba and last build commit is d61323d6543c581b320ce7972f169f04dd165eba 06:46:27 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named triggerBuild (to a value of type Boolean) which could lead to memory leaks or other issues. 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // script 06:46:27 [Pipeline] script 06:46:27 [Pipeline] { 06:46:27 [Pipeline] readMavenPom 06:46:27 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named pom (to a value of type Model) which could lead to memory leaks or other issues. 06:46:27 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named release (to a value of type String) which could lead to memory leaks or other issues. 06:46:27 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named buildNumber (to a value of type String) which could lead to memory leaks or other issues. 06:46:27 Did you forget the `def` keyword? WorkflowScript seems to be setting a field named buildVersion (to a value of type GStringImpl) which could lead to memory leaks or other issues. 06:46:27 [Pipeline] echo 06:46:27 No changes and no update in Silverpeas since the last build 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // script 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Build the project) 06:46:27 Stage "Build the project" skipped due to when conditional 06:46:27 [Pipeline] getContext 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Check POM parent version) 06:46:27 Stage "Build the project" skipped due to when conditional 06:46:27 [Pipeline] getContext 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Update POM parent) 06:46:27 Stage "Build the project" skipped due to when conditional 06:46:27 [Pipeline] getContext 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Update dependency on Silverpeas) 06:46:27 Stage "Build the project" skipped due to when conditional 06:46:27 [Pipeline] getContext 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Build and Publish) 06:46:27 Stage "Build the project" skipped due to when conditional 06:46:27 [Pipeline] getContext 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Create YAML build report) 06:46:27 [Pipeline] script 06:46:27 [Pipeline] { 06:46:27 [Pipeline] sh 06:46:28 + mkdir -p target 06:46:28 [Pipeline] sh 06:46:28 + mv build.yaml target/ 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // script 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] stage 06:46:28 [Pipeline] { (Declarative: Post Actions) 06:46:28 [Pipeline] step 06:46:28 [Pipeline] script 06:46:28 [Pipeline] { 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // script 06:46:28 [Pipeline] archiveArtifacts 06:46:28 Archiving artifacts 06:46:28 Enregistrement des empreintes numériques 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // withEnv 06:46:28 [Pipeline] } 06:46:28 $ docker stop --time=1 4ed70fb4451876b2c8eaeeff2d755c1328dc98b234de51165ca27531a9f52e1e 06:46:29 $ docker rm -f --volumes 4ed70fb4451876b2c8eaeeff2d755c1328dc98b234de51165ca27531a9f52e1e 06:46:29 [Pipeline] // withDockerContainer 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // withEnv 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // node 06:46:29 [Pipeline] End of Pipeline 06:46:29 Finished: SUCCESS