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