06:46:19 Démarré par le projet amont "Silverpeas_Stable_AutoDeploy" de numéro de build 369 06:46:19 Causé à l'origine par : 06:46:19 Lancé par une alarme périodique 06:46:19 Running as userbuild 06:46:19 Obtained src/builds/mobile/Jenkinsfile from git https://github.com/Silverpeas/Jenkins-Pipelines.git 06:46:19 [Pipeline] Start of Pipeline 06:46:20 [Pipeline] node 06:46:20 Running on Jenkins in /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy 06:46:20 [Pipeline] { 06:46:20 [Pipeline] stage 06:46:20 [Pipeline] { (Declarative: Checkout SCM) 06:46:20 [Pipeline] checkout 06:46:20 Selected Git installation does not exist. Using Default 06:46:20 The recommended git tool is: NONE 06:46:20 No credentials specified 06:46:20 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy/.git # timeout=10 06:46:20 Fetching changes from the remote Git repository 06:46:20 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/Jenkins-Pipelines.git # timeout=10 06:46:20 Cleaning workspace 06:46:20 > /usr/bin/git rev-parse --verify HEAD # timeout=10 06:46:20 Resetting working tree 06:46:20 > /usr/bin/git reset --hard # timeout=10 06:46:20 > /usr/bin/git clean -fdx # timeout=10 06:46:20 Fetching upstream changes from https://github.com/Silverpeas/Jenkins-Pipelines.git 06:46:20 > /usr/bin/git --version # timeout=10 06:46:20 > git --version # 'git version 2.43.0' 06:46:20 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/Jenkins-Pipelines.git +refs/heads/*:refs/remotes/origin/* # timeout=10 06:46:21 > /usr/bin/git rev-parse refs/remotes/origin/master^{commit} # timeout=10 06:46:21 Checking out Revision 08023d811205f6aba0cc1af783597b4af757a954 (refs/remotes/origin/master) 06:46:21 > /usr/bin/git config core.sparsecheckout # timeout=10 06:46:21 > /usr/bin/git checkout -f 08023d811205f6aba0cc1af783597b4af757a954 # timeout=10 06:46:21 Commit message: "Fix condition testing in the release pipeline for Silverpeas-Sso. In this same pipeline, give the version of the Docker image to use (6.4 currently). Idem for the auto build pipeline for Silverpeas-Sso." 06:46:21 > /usr/bin/git rev-list --no-walk e8468bf49647ac63ce0c1464a25fb5c963108a3f # timeout=10 06:46:21 [Pipeline] } 06:46:21 [Pipeline] // stage 06:46:21 [Pipeline] withEnv 06:46:21 [Pipeline] { 06:46:22 [Pipeline] isUnix 06:46:22 [Pipeline] withEnv 06:46:22 [Pipeline] { 06:46:22 [Pipeline] sh 06:46:22 + docker inspect -f . silverpeas/silverbuild:6.4 06:46:22 . 06:46:22 [Pipeline] } 06:46:22 [Pipeline] // withEnv 06:46:22 [Pipeline] withDockerContainer 06:46:22 Jenkins does not seem to be running inside a container 06:46:22 $ 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:22 $ docker top 11d694ea1f925917069deeeeb8890e3ea01d7efec6b0380c2772bce2959eea08 -eo pid,comm 06:46:22 [Pipeline] { 06:46:22 [Pipeline] withEnv 06:46:22 [Pipeline] { 06:46:22 [Pipeline] stage 06:46:22 [Pipeline] { (Resolve dependency on Silverpeas) 06:46:22 [Pipeline] script 06:46:22 [Pipeline] { 06:46:22 [Pipeline] echo 06:46:22 Working on branch 6.4.x 06:46:22 [Pipeline] copyArtifacts 06:46:22 Copied 1 artifact from "Silverpeas_Stable_AutoDeploy" build number 369 06:46:22 [Pipeline] readYaml 06:46:22 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:22 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:22 [Pipeline] sh 06:46:23 + rm -f build.yaml 06:46:23 [Pipeline] } 06:46:23 [Pipeline] // script 06:46:23 [Pipeline] echo 06:46:23 Parent version is 1.6.2 06:46:23 [Pipeline] echo 06:46:23 Silverpeas version is 6.4.3-build250227 06:46:23 [Pipeline] } 06:46:23 [Pipeline] // stage 06:46:23 [Pipeline] stage 06:46:23 [Pipeline] { (Prepare the project) 06:46:23 [Pipeline] git 06:46:23 The recommended git tool is: /usr/bin/git 06:46:23 using credential cacc0467-7c85-41d1-bf4e-eaa470dd5e59 06:46:23 Warning: JENKINS-30600: special launcher org.jenkinsci.plugins.docker.workflow.WithContainerStep$Decorator$1@45097b14; decorates hudson.Launcher$LocalLauncher@58a3e0fe will be ignored (a typical symptom is the Git executable not being run inside a designated container) 06:46:23 > /usr/bin/git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/Silverpeas_Mobile_Stable_AutoDeploy/.git # timeout=10 06:46:23 Fetching changes from the remote Git repository 06:46:23 > /usr/bin/git config remote.origin.url https://github.com/Silverpeas/silverpeasmobile # timeout=10 06:46:23 Fetching upstream changes from https://github.com/Silverpeas/silverpeasmobile 06:46:23 > /usr/bin/git --version # timeout=10 06:46:23 > git --version # 'git version 2.43.0' 06:46:23 using GIT_ASKPASS to set credentials GitHub Credentials For Jenkins 06:46:23 > /usr/bin/git fetch --tags --force --progress -- https://github.com/Silverpeas/silverpeasmobile +refs/heads/*:refs/remotes/origin/* # timeout=10 06:46:23 > /usr/bin/git rev-parse refs/remotes/origin/6.4.x^{commit} # timeout=10 06:46:23 Checking out Revision 09b7028614a7a602c3511183fcd94127f9cc4642 (refs/remotes/origin/6.4.x) 06:46:23 > /usr/bin/git config core.sparsecheckout # timeout=10 06:46:23 > /usr/bin/git checkout -f 09b7028614a7a602c3511183fcd94127f9cc4642 # timeout=10 06:46:23 > /usr/bin/git branch -a -v --no-abbrev # timeout=10 06:46:23 > /usr/bin/git branch -D 6.4.x # timeout=10 06:46:23 > /usr/bin/git checkout -b 6.4.x 09b7028614a7a602c3511183fcd94127f9cc4642 # timeout=10 06:46:24 Commit message: "Update dependency on Silverpeas to version 6.4.3-build250227" 06:46:24 > /usr/bin/git rev-list --no-walk 09b7028614a7a602c3511183fcd94127f9cc4642 # timeout=10 06:46:24 [Pipeline] script 06:46:24 [Pipeline] { 06:46:24 [Pipeline] copyArtifacts 06:46:24 Copied 1 artifact from "Silverpeas_Mobile_Stable_AutoDeploy" build number 271 06:46:24 [Pipeline] readYaml 06:46: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. 06:46:24 [Pipeline] sh 06:46:24 + git rev-parse HEAD 06:46:24 [Pipeline] echo 06:46:24 Current commit is 09b7028614a7a602c3511183fcd94127f9cc4642 and last build commit is 09b7028614a7a602c3511183fcd94127f9cc4642 06:46:24 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:24 [Pipeline] } 06:46:24 [Pipeline] // script 06:46:24 [Pipeline] script 06:46:24 [Pipeline] { 06:46:24 [Pipeline] readMavenPom 06:46:24 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:24 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:24 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:24 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:24 [Pipeline] echo 06:46:24 No changes and no update in Silverpeas since the last build 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // script 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] stage 06:46:24 [Pipeline] { (Build the project) 06:46:24 Stage "Build the project" skipped due to when conditional 06:46:24 [Pipeline] getContext 06:46:24 [Pipeline] stage 06:46:24 [Pipeline] { (Check POM parent version) 06:46:24 Stage "Build the project" skipped due to when conditional 06:46:24 [Pipeline] getContext 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] stage 06:46:24 [Pipeline] { (Update POM parent) 06:46:24 Stage "Build the project" skipped due to when conditional 06:46:24 [Pipeline] getContext 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] stage 06:46:24 [Pipeline] { (Update dependency on Silverpeas) 06:46:24 Stage "Build the project" skipped due to when conditional 06:46:24 [Pipeline] getContext 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] stage 06:46:24 [Pipeline] { (Build and Publish) 06:46:24 Stage "Build the project" skipped due to when conditional 06:46:24 [Pipeline] getContext 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] } 06:46:24 [Pipeline] // stage 06:46:24 [Pipeline] stage 06:46:24 [Pipeline] { (Create YAML build report) 06:46:24 [Pipeline] script 06:46:24 [Pipeline] { 06:46:24 [Pipeline] sh 06:46:24 + mkdir -p target 06:46:24 [Pipeline] sh 06:46:25 + mv build.yaml target/ 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // script 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // stage 06:46:25 [Pipeline] stage 06:46:25 [Pipeline] { (Declarative: Post Actions) 06:46:25 [Pipeline] step 06:46:25 [Pipeline] script 06:46:25 [Pipeline] { 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // script 06:46:25 [Pipeline] archiveArtifacts 06:46:25 Archiving artifacts 06:46:25 Enregistrement des empreintes numériques 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // stage 06:46:25 [Pipeline] } 06:46:25 [Pipeline] // withEnv 06:46:25 [Pipeline] } 06:46:25 $ docker stop --time=1 11d694ea1f925917069deeeeb8890e3ea01d7efec6b0380c2772bce2959eea08 06:46:26 $ docker rm -f --volumes 11d694ea1f925917069deeeeb8890e3ea01d7efec6b0380c2772bce2959eea08 06:46:26 [Pipeline] // withDockerContainer 06:46:26 [Pipeline] } 06:46:26 [Pipeline] // withEnv 06:46:26 [Pipeline] } 06:46:26 [Pipeline] // node 06:46:26 [Pipeline] End of Pipeline 06:46:26 Finished: SUCCESS