06:46:24 Démarré par le projet amont "Silverpeas_Stable_AutoDeploy" de numéro de build 552 06:46:24 Causé à l'origine par : 06:46:24 Lancé par une alarme périodique 06:46:24 Running as userbuild 06:46:25 Obtained src/builds/mobile/Jenkinsfile from git https://github.com/Silverpeas/Jenkins-Pipelines.git 06:46:25 [Pipeline] Start of Pipeline 06:46:25 [Pipeline] node 06:46:25 Running on Jenkins in /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy 06:46:25 [Pipeline] { 06:46:25 [Pipeline] stage 06:46:25 [Pipeline] { (Declarative: Checkout SCM) 06:46:25 [Pipeline] checkout 06:46:25 Selected Git installation does not exist. Using Default 06:46:25 The recommended git tool is: NONE 06:46:25 No credentials specified 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/Jenkins-Pipelines.git # timeout=10 06:46:25 Cleaning workspace 06:46:25 > /usr/bin/git rev-parse --verify HEAD # timeout=10 06:46:25 Resetting working tree 06:46:25 > /usr/bin/git reset --hard # timeout=10 06:46:25 > /usr/bin/git clean -fdx # timeout=10 06:46:25 Fetching upstream changes from https://github.com/Silverpeas/Jenkins-Pipelines.git 06:46:25 > /usr/bin/git --version # timeout=10 06:46:25 > git --version # 'git version 2.43.0' 06:46:25 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/Jenkins-Pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 06:46:26 > /usr/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10 06:46:26 Checking out Revision 5b79d885d26d617ef109b485fb9832a9185c5ce0 (refs/remotes/origin/master) 06:46:26 > /usr/bin/git config core.sparsecheckout # timeout=10 06:46:26 > /usr/bin/git checkout -f 5b79d885d26d617ef109b485fb9832a9185c5ce0 # timeout=10 06:46:26 Commit message: "In the pipeline to construct a Docker image for building a Silverpeas project, add a new stage in which we switch to the git branch that is related to the version of the Docker image to generate. If such branch doesn't yet exist, then it is created." 06:46:26 > /usr/bin/git rev-list --no-walk 5b79d885d26d617ef109b485fb9832a9185c5ce0 # timeout=10 06:46:26 [Pipeline] } 06:46:26 [Pipeline] // stage 06:46:26 [Pipeline] withEnv 06:46:26 [Pipeline] { 06:46:26 [Pipeline] isUnix 06:46:26 [Pipeline] withEnv 06:46:26 [Pipeline] { 06:46:26 [Pipeline] sh 06:46:26 + docker inspect -f . silverpeas/silverbuild:6.4 06:46:26 . 06:46:26 [Pipeline] } 06:46:26 [Pipeline] // withEnv 06:46:26 [Pipeline] withDockerContainer 06:46:26 Jenkins does not seem to be running inside a container 06:46:26 $ 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:27 $ docker top 1e58a31d5ad2f12972ee756acd008ffd50c605c5d0bc9a1ca3c1e3a2924980e9 -eo pid,comm 06:46:27 [Pipeline] { 06:46:27 [Pipeline] withEnv 06:46:27 [Pipeline] { 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Resolve dependency on Silverpeas) 06:46:27 [Pipeline] script 06:46:27 [Pipeline] { 06:46:27 [Pipeline] echo 06:46:27 Working on branch 6.4.x 06:46:27 [Pipeline] copyArtifacts 06:46:27 Copied 1 artifact from "Silverpeas_Stable_AutoDeploy" build number 552 06:46:27 [Pipeline] readYaml 06:46:27 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:27 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:27 [Pipeline] sh 06:46:27 + rm -f build.yaml 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // script 06:46:27 [Pipeline] echo 06:46:27 Parent version is 1.6.3 06:46:27 [Pipeline] echo 06:46:27 Silverpeas version is 6.4.8-build260810 06:46:27 [Pipeline] } 06:46:27 [Pipeline] // stage 06:46:27 [Pipeline] stage 06:46:27 [Pipeline] { (Prepare the project) 06:46:27 [Pipeline] git 06:46:27 The recommended git tool is: /usr/bin/git 06:46:27 using credential cacc0467-7c85-41d1-bf4e-eaa470dd5e59 06:46:27 Warning: JENKINS-30600: special launcher org.jenkinsci.plugins.docker.workflow.WithContainerStep$Decorator$1@9ca0eaa; decorates hudson.Launcher$LocalLauncher@763c7029 will be ignored (a typical symptom is the Git executable not being run inside a designated container) 06:46:27 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy/.git # timeout=10 06:46:27 Fetching changes from the remote Git repository 06:46:27 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/silverpeasmobile # timeout=10 06:46:27 Fetching upstream changes from https://github.com/Silverpeas/silverpeasmobile 06:46:27 > /usr/bin/git --version # timeout=10 06:46:27 > git --version # 'git version 2.43.0' 06:46:27 using GIT_ASKPASS to set credentials GitHub Credentials For Jenkins 06:46:27 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/silverpeasmobile +refs/heads/*:refs/remotes/origin/* # timeout=10 06:46:28 > /usr/bin/git rev-parse refs/remotes/origin/6.4.x^{commit} # timeout=10 06:46:28 Checking out Revision 96d9b06c4e2f91e90436aed63ee312ac894d9cf2 (refs/remotes/origin/6.4.x) 06:46:28 > /usr/bin/git config core.sparsecheckout # timeout=10 06:46:28 > /usr/bin/git checkout -f 96d9b06c4e2f91e90436aed63ee312ac894d9cf2 # timeout=10 06:46:28 > /usr/bin/git branch -a -v --no-abbrev # timeout=10 06:46:28 > /usr/bin/git branch -D 6.4.x # timeout=10 06:46:28 > /usr/bin/git checkout -b 6.4.x 96d9b06c4e2f91e90436aed63ee312ac894d9cf2 # timeout=10 06:46:28 Commit message: "Update dependency on Silverpeas to version 6.4.8-build260810" 06:46:28 > /usr/bin/git rev-list --no-walk d61323d6543c581b320ce7972f169f04dd165eba # timeout=10 06:46:28 [Pipeline] script 06:46:28 [Pipeline] { 06:46:28 [Pipeline] copyArtifacts 06:46:28 Copied 1 artifact from "Silverpeas_Mobile_Stable_AutoDeploy" build number 422 06:46:28 [Pipeline] readYaml 06:46:28 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:28 [Pipeline] sh 06:46:28 + git rev-parse HEAD 06:46:28 [Pipeline] echo 06:46:28 Current commit is 96d9b06c4e2f91e90436aed63ee312ac894d9cf2 and last build commit is 96d9b06c4e2f91e90436aed63ee312ac894d9cf2 06:46:28 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:28 [Pipeline] } 06:46:28 [Pipeline] // script 06:46:28 [Pipeline] script 06:46:28 [Pipeline] { 06:46:28 [Pipeline] readMavenPom 06:46:28 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:28 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:28 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:28 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:28 [Pipeline] echo 06:46:28 No changes and no update in Silverpeas since the last build 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] { (Build the project) 06:46:28 Stage "Build the project" skipped due to when conditional 06:46:28 [Pipeline] getContext 06:46:28 [Pipeline] stage 06:46:28 [Pipeline] { (Check POM parent version) 06:46:28 Stage "Build the project" skipped due to when conditional 06:46:28 [Pipeline] getContext 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] stage 06:46:28 [Pipeline] { (Update POM parent) 06:46:28 Stage "Build the project" skipped due to when conditional 06:46:28 [Pipeline] getContext 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] stage 06:46:28 [Pipeline] { (Update dependency on Silverpeas) 06:46:28 Stage "Build the project" skipped due to when conditional 06:46:28 [Pipeline] getContext 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] stage 06:46:28 [Pipeline] { (Build and Publish) 06:46:28 Stage "Build the project" skipped due to when conditional 06:46:28 [Pipeline] getContext 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] } 06:46:28 [Pipeline] // stage 06:46:28 [Pipeline] stage 06:46:28 [Pipeline] { (Create YAML build report) 06:46:28 [Pipeline] script 06:46:28 [Pipeline] { 06:46:28 [Pipeline] sh 06:46:29 + mkdir -p target 06:46:29 [Pipeline] sh 06:46:29 + mv build.yaml target/ 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // script 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // stage 06:46:29 [Pipeline] stage 06:46:29 [Pipeline] { (Declarative: Post Actions) 06:46:29 [Pipeline] step 06:46:29 [Pipeline] script 06:46:29 [Pipeline] { 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // script 06:46:29 [Pipeline] archiveArtifacts 06:46:29 Archiving artifacts 06:46:29 Enregistrement des empreintes numériques 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // stage 06:46:29 [Pipeline] } 06:46:29 [Pipeline] // withEnv 06:46:29 [Pipeline] } 06:46:29 $ docker stop --time=1 1e58a31d5ad2f12972ee756acd008ffd50c605c5d0bc9a1ca3c1e3a2924980e9 06:46:30 $ docker rm -f --volumes 1e58a31d5ad2f12972ee756acd008ffd50c605c5d0bc9a1ca3c1e3a2924980e9 06:46:31 [Pipeline] // withDockerContainer 06:46:31 [Pipeline] } 06:46:31 [Pipeline] // withEnv 06:46:31 [Pipeline] } 06:46:31 [Pipeline] // node 06:46:31 [Pipeline] End of Pipeline 06:46:31 Finished: SUCCESS