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