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