01:21:21 Démarré par le projet amont "Silverpeas_6.3.x_AutoDeploy" de numéro de build 286 01:21:21 Causé à l'origine par : 01:21:21 Lancé par une alarme périodique 01:21:21 Running as userbuild 01:21:21 Obtained src/builds/mobile/Jenkinsfile from git https://github.com/Silverpeas/Jenkins-Pipelines.git 01:21:21 [Pipeline] Start of Pipeline 01:21:22 [Pipeline] node 01:21:22 Running on Jenkins in /var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_AutoDeploy 01:21:22 [Pipeline] { 01:21:22 [Pipeline] stage 01:21:22 [Pipeline] { (Declarative: Checkout SCM) 01:21:22 [Pipeline] checkout 01:21:22 Selected Git installation does not exist. Using Default 01:21:22 The recommended git tool is: NONE 01:21:22 No credentials specified 01:21:22 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_AutoDeploy/.git # timeout=10 01:21:22 Fetching changes from the remote Git repository 01:21:22 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/Jenkins-Pipelines.git # timeout=10 01:21:22 Cleaning workspace 01:21:22 > /usr/bin/git rev-parse --verify HEAD # timeout=10 01:21:22 Resetting working tree 01:21:22 > /usr/bin/git reset --hard # timeout=10 01:21:22 > /usr/bin/git clean -fdx # timeout=10 01:21:22 Fetching upstream changes from https://github.com/Silverpeas/Jenkins-Pipelines.git 01:21:22 > /usr/bin/git --version # timeout=10 01:21:22 > git --version # 'git version 2.43.0' 01:21:22 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/Jenkins-Pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 01:21:22 > /usr/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10 01:21:22 Checking out Revision 01d06ccb34ffbca958998fce357470ddc43cbd57 (refs/remotes/origin/master) 01:21:22 > /usr/bin/git config core.sparsecheckout # timeout=10 01:21:22 > /usr/bin/git checkout -f 01d06ccb34ffbca958998fce357470ddc43cbd57 # timeout=10 01:21:22 Commit message: "In all Jenkinsfiles, when updating the parent POM version, do it explicitly without any resolution" 01:21:22 > /usr/bin/git rev-list --no-walk 01d06ccb34ffbca958998fce357470ddc43cbd57 # timeout=10 01:21:22 [Pipeline] } 01:21:22 [Pipeline] // stage 01:21:22 [Pipeline] withEnv 01:21:22 [Pipeline] { 01:21:22 [Pipeline] isUnix 01:21:22 [Pipeline] withEnv 01:21:22 [Pipeline] { 01:21:22 [Pipeline] sh 01:21:23 + docker inspect -f . silverpeas/silverbuild:6.3.3 01:21:23 . 01:21:23 [Pipeline] } 01:21:23 [Pipeline] // withEnv 01:21:23 [Pipeline] withDockerContainer 01:21:23 Jenkins does not seem to be running inside a container 01:21:23 $ 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_6.3.x_AutoDeploy -v /var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_AutoDeploy:/var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_AutoDeploy:rw,z -v /var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_AutoDeploy@tmp:/var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_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.3.3 cat 01:21:23 $ docker top 3e01a03b30af8faa60504b33c01d732de9b8508f14cfdad758d63dee0e743284 -eo pid,comm 01:21:23 [Pipeline] { 01:21:23 [Pipeline] withEnv 01:21:23 [Pipeline] { 01:21:23 [Pipeline] stage 01:21:23 [Pipeline] { (Resolve dependency on Silverpeas) 01:21:23 [Pipeline] script 01:21:23 [Pipeline] { 01:21:23 [Pipeline] echo 01:21:23 Working on branch 6.3.x 01:21:23 [Pipeline] copyArtifacts 01:21:23 Copied 1 artifact from "Silverpeas_6.3.x_AutoDeploy" build number 286 01:21:23 [Pipeline] readYaml 01:21:23 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. 01:21:23 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. 01:21:23 [Pipeline] sh 01:21:23 + rm -f build.yaml 01:21:23 [Pipeline] } 01:21:23 [Pipeline] // script 01:21:23 [Pipeline] echo 01:21:23 Parent version is 1.5.3 01:21:23 [Pipeline] echo 01:21:23 Silverpeas version is 6.3.7-build250214 01:21:23 [Pipeline] } 01:21:23 [Pipeline] // stage 01:21:23 [Pipeline] stage 01:21:23 [Pipeline] { (Prepare the project) 01:21:23 [Pipeline] git 01:21:23 The recommended git tool is: /usr/bin/git 01:21:23 using credential cacc0467-7c85-41d1-bf4e-eaa470dd5e59 01:21:23 Warning: JENKINS-30600: special launcher org.jenkinsci.plugins.docker.workflow.WithContainerStep$Decorator$1@27586373; decorates hudson.Launcher$LocalLauncher@1853ae5c will be ignored (a typical symptom is the Git executable not being run inside a designated container) 01:21:23 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_6.3.x_AutoDeploy/.git # timeout=10 01:21:23 Fetching changes from the remote Git repository 01:21:23 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/silverpeasmobile # timeout=10 01:21:23 Fetching upstream changes from https://github.com/Silverpeas/silverpeasmobile 01:21:23 > /usr/bin/git --version # timeout=10 01:21:23 > git --version # 'git version 2.43.0' 01:21:23 using GIT_ASKPASS to set credentials GitHub Credentials For Jenkins 01:21:23 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/silverpeasmobile +refs/heads/*:refs/remotes/origin/* # timeout=10 01:21:24 > /usr/bin/git rev-parse refs/remotes/origin/6.3.x^{commit} # timeout=10 01:21:24 Checking out Revision defa63b4934e025329da4b267c4ca7f8968d7347 (refs/remotes/origin/6.3.x) 01:21:24 > /usr/bin/git config core.sparsecheckout # timeout=10 01:21:24 > /usr/bin/git checkout -f defa63b4934e025329da4b267c4ca7f8968d7347 # timeout=10 01:21:24 > /usr/bin/git branch -a -v --no-abbrev # timeout=10 01:21:24 > /usr/bin/git branch -D 6.3.x # timeout=10 01:21:24 > /usr/bin/git checkout -b 6.3.x defa63b4934e025329da4b267c4ca7f8968d7347 # timeout=10 01:21:24 Commit message: "Update dependency on Silverpeas to version 6.3.7-build250214" 01:21:24 > /usr/bin/git rev-list --no-walk defa63b4934e025329da4b267c4ca7f8968d7347 # timeout=10 01:21:24 [Pipeline] script 01:21:24 [Pipeline] { 01:21:24 [Pipeline] copyArtifacts 01:21:24 Copied 1 artifact from "Silverpeas_Mobile_6.3.x_AutoDeploy" build number 257 01:21:24 [Pipeline] readYaml 01:21:24 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. 01:21:24 [Pipeline] sh 01:21:25 + git rev-parse HEAD 01:21:25 [Pipeline] echo 01:21:25 Current commit is defa63b4934e025329da4b267c4ca7f8968d7347 and last build commit is defa63b4934e025329da4b267c4ca7f8968d7347 01:21:25 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. 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // script 01:21:25 [Pipeline] script 01:21:25 [Pipeline] { 01:21:25 [Pipeline] readMavenPom 01:21:25 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. 01:21:25 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. 01:21:25 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. 01:21:25 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. 01:21:25 [Pipeline] echo 01:21:25 No changes and no update in Silverpeas since the last build 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // script 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Build the project) 01:21:25 Stage "Build the project" skipped due to when conditional 01:21:25 [Pipeline] getContext 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Check POM parent version) 01:21:25 Stage "Build the project" skipped due to when conditional 01:21:25 [Pipeline] getContext 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Update POM parent) 01:21:25 Stage "Build the project" skipped due to when conditional 01:21:25 [Pipeline] getContext 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Update dependency on Silverpeas) 01:21:25 Stage "Build the project" skipped due to when conditional 01:21:25 [Pipeline] getContext 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Build and Publish) 01:21:25 Stage "Build the project" skipped due to when conditional 01:21:25 [Pipeline] getContext 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Create YAML build report) 01:21:25 [Pipeline] script 01:21:25 [Pipeline] { 01:21:25 [Pipeline] sh 01:21:25 + mkdir -p target 01:21:25 [Pipeline] sh 01:21:25 + mv build.yaml target/ 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // script 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // stage 01:21:25 [Pipeline] stage 01:21:25 [Pipeline] { (Declarative: Post Actions) 01:21:25 [Pipeline] step 01:21:25 [Pipeline] script 01:21:25 [Pipeline] { 01:21:25 [Pipeline] } 01:21:25 [Pipeline] // script 01:21:25 [Pipeline] archiveArtifacts 01:21:25 Archiving artifacts 01:21:26 Enregistrement des empreintes numériques 01:21:26 [Pipeline] } 01:21:26 [Pipeline] // stage 01:21:26 [Pipeline] } 01:21:26 [Pipeline] // withEnv 01:21:26 [Pipeline] } 01:21:26 $ docker stop --time=1 3e01a03b30af8faa60504b33c01d732de9b8508f14cfdad758d63dee0e743284 01:21:27 $ docker rm -f --volumes 3e01a03b30af8faa60504b33c01d732de9b8508f14cfdad758d63dee0e743284 01:21:27 [Pipeline] // withDockerContainer 01:21:27 [Pipeline] } 01:21:27 [Pipeline] // withEnv 01:21:27 [Pipeline] } 01:21:27 [Pipeline] // node 01:21:27 [Pipeline] End of Pipeline 01:21:27 Finished: SUCCESS