Démarré à distance par l'hôte 140.82.115.33140.82.115.33Démarré à distance par l'hôte 140.82.115.5140.82.115.567c8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterc8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterc8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git67a8baa932ba0e28a8c5f04cee2a26ec8efdddb0faa8baa932ba0e28a8c5f04cee2a26ec8efdddb0farefs/remotes/origin/mastera8baa932ba0e28a8c5f04cee2a26ec8efdddb0faa8baa932ba0e28a8c5f04cee2a26ec8efdddb0farefs/remotes/origin/mastera8baa932ba0e28a8c5f04cee2a26ec8efdddb0faa8baa932ba0e28a8c5f04cee2a26ec8efdddb0farefs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Ssohttps://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/lastStableBuild/artifacthttps://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/changeshttps://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/lastStableBuild/https://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/lastStableBuild/testReportfalseResolve dependency on SilverpeasCheckout the projectCheck POM parent versionCheck Silverpeas versionUpdate POM parentUpdate dependency on SilverpeasBuild and PublishCreate YAML build reportbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build260916107887111065Silverpeas_SSO_AutoDeploy 2.0-build26091667false6759851SUCCESS1789562602944https://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/67/- pom.xmla84861023c68d264c0bdc66c980536e07d890d041789562589000https://integration.silverpeas.org/jenkins/user/devteamdevteamdevteam@silverpeas.netUpdate parent POM to version 2.0-build260821
2026-09-16 14:43:09 +0200a84861023c68d264c0bdc66c980536e07d890d04Update parent POM to version 2.0-build260821editpom.xml
- pom.xmla8baa932ba0e28a8c5f04cee2a26ec8efdddb0fa1789562592000https://integration.silverpeas.org/jenkins/user/devteamdevteamdevteam@silverpeas.netUpdate dependency on Silverpeas to version 6.5-build260914
2026-09-16 14:43:12 +0200a8baa932ba0e28a8c5f04cee2a26ec8efdddb0faUpdate dependency on Silverpeas to version 6.5-build260914editpom.xml
githttps://integration.silverpeas.org/jenkins/user/devteamdevteamdevteamfalseDémarré par l'utilisateur Miguel MoquillonmmoquillonMiguel Moquillon66c8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterc8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterc8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git66a7623fd369140a4cfe4b997aa7a28e58d286d1cda7623fd369140a4cfe4b997aa7a28e58d286d1cdrefs/remotes/origin/mastera7623fd369140a4cfe4b997aa7a28e58d286d1cda7623fd369140a4cfe4b997aa7a28e58d286d1cdrefs/remotes/origin/mastera7623fd369140a4cfe4b997aa7a28e58d286d1cda7623fd369140a4cfe4b997aa7a28e58d286d1cdrefs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Ssobuild.yamlbuild.yamltarget/build.yamlfalse2.0-build260916118479111065Silverpeas_SSO_AutoDeploy 2.0-build26091666false6659842SUCCESS1789562568622https://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/66/- src/releases/docker-build/Jenkinsfilec23612b1bbd434fb8b6627cef9dd95f58313f0031786027778000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the pipeline of construction of a Docker image for building
Silverpeas projects. Now the Dockerfile is updated only for latest
Docker image before its construction. Otherwise, pass the information as
arguments in the Docker image construction. No more git tags as the
Docker image with a given tag can be overridden by a new image with the
same tag (after an update of the Dockerfile).
2026-08-06 16:49:38 +0200c23612b1bbd434fb8b6627cef9dd95f58313f003Update the pipeline of construction of a Docker image for buildingeditsrc/releases/docker-build/Jenkinsfile
- src/releases/docker-build/Jenkinsfile5b79d885d26d617ef109b485fb9832a9185c5ce01786088952000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comIn 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.
2026-08-07 09:49:12 +02005b79d885d26d617ef109b485fb9832a9185c5ce0In 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.editsrc/releases/docker-build/Jenkinsfile
- src/releases/silverpeas/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile7e3556671c10e320bbd1de57e3638d1b427e63131788341397000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFor the pipelines dedicated to build a build version of Silverpeas and
to release a stable version of Silverpeas (from a build version), mount
in the Docker container the file ~/.gradle/gradle.properties
configuration file in which should be defined the credentials for
publishing artefacts into our Maven/Gradle repo.
2026-09-02 11:29:57 +02007e3556671c10e320bbd1de57e3638d1b427e6313For the pipelines dedicated to build a build version of Silverpeas andeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
- src/releases/docker-build/Jenkinsfileb3a0a7bf423a3407c3bc6980f30a0c6ee678b5ae1788354644000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comNow by default Java version is 21 in the pipeline for building the project build Docker image
2026-09-02 15:10:44 +0200b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeNow by default Java version is 21 in the pipeline for building the project build Docker imageeditsrc/releases/docker-build/Jenkinsfile
- src/releases/silverpeas-doc/Jenkinsfilef64daadcc7bd085a2b858d8a925881e34c73162e1788856387000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comPublish the documentation of the REST API and guard it against silent failures
The specification of the REST API is produced by the resolve goal of Swagger,
bound to the compile phase and forking no compilation, so the site lifecycle
alone would publish a page without any specification. Each project therefore
gets a dedicated step running the default lifecycle before the site one, on its
own documentation module.
The generation is silent about its own failures: it reports a success even when
it produces nothing, and an incomplete documentation would be published
unnoticed. Two checks now stand in the way:
* checkRestApiDoc fails the build when a specification declares fewer paths
than expected, currently 150 for Core and 60 for the applications;
* checkCommonResponses compares the specifications with each other. The
response common to every endpoint is brought by the CommonResponsesFilter
class of Swagger, of which each project has its own copy, so the check
fails both when an operation has lost that response and when the copies have
drifted apart and word it differently.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-08 10:33:07 +0200f64daadcc7bd085a2b858d8a925881e34c73162ePublish the documentation of the REST API and guard it against silent failureseditsrc/releases/silverpeas-doc/Jenkinsfile
- src/releases/silverpeas-doc/Jenkinsfilef8d46a4f391399737486d50523ff3627cf1860cd1789470418000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comCheck the documentation of the REST API declares an info section and summarizes
The published specification lacked the info section OpenAPI requires, and the
check didn't notice: it was counting the paths only. A renderer displays nothing
at all of such a document, so this is as bad a failure as an empty one.
The count of the operations carrying a summary is checked as well. None of the
tools reads the javadoc, hence an operation without any summary means the scan
has run over artefacts built out of the branch being documented -- a mistake the
more likely as the projects of a same machine share one local Maven repository.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 13:06:58 +0200f8d46a4f391399737486d50523ff3627cf1860cdCheck the documentation of the REST API declares an info section and summarizeseditsrc/releases/silverpeas-doc/Jenkinsfile
- src/releases/silverpeas-doc/Jenkinsfilee3e30163f69964e794525f171a36018c0bcc1e8a1789480465000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comWord the check of the common responses after the merge of the filter
The class bringing the response common to every endpoint used to be duplicated
in each project, and the check was watching the copies for a drift. It now comes
from core-rs, so what the check guards against is a project documented against
another version of that class than the one being released.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-15 15:54:25 +0200e3e30163f69964e794525f171a36018c0bcc1e8aWord the check of the common responses after the merge of the filtereditsrc/releases/silverpeas-doc/Jenkinsfile
- src/releases/docker-build/Jenkinsfilec8dc7ef50e04c1b811eb42acbb89b17d98f982d71789485078000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFix shell bad syntax
2026-09-15 17:11:18 +0200c8dc7ef50e04c1b811eb42acbb89b17d98f982d7Fix shell bad syntaxeditsrc/releases/docker-build/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse67https://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/67/65https://integration.silverpeas.org/jenkins/job/Silverpeas_SSO_AutoDeploy/65/