Démarré à distance par l'hôte 140.82.115.12140.82.115.12Started by GitHub push by mmoqui302c8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterc8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterc8dc7ef50e04c1b811eb42acbb89b17d98f982d7c8dc7ef50e04c1b811eb42acbb89b17d98f982d7refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git302656133956dae4a2a6f37b475fcf3eddb1659f429656133956dae4a2a6f37b475fcf3eddb1659f429refs/remotes/origin/master656133956dae4a2a6f37b475fcf3eddb1659f429656133956dae4a2a6f37b475fcf3eddb1659f429refs/remotes/origin/master656133956dae4a2a6f37b475fcf3eddb1659f429656133956dae4a2a6f37b475fcf3eddb1659f429refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom302a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom302c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projecthttps://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/lastBuild/artifacthttps://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/changeshttps://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/lastBuild/https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/lastBuild/testReportfalsePrepare the buildBuild and Publish dependencies definitionBuild and Publish test dependencies definitionBuild and publish project definitionCreate YAML build reportbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609184355140091Silverpeas_Project_Definition_AutoDeploy 2.0-build260918302false30260047SUCCESS1789748420693https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/302/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/Jenkinsfilesrc/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/Jenkinsfilesrc/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/Jenkinsfilesrc/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/Jenkinsfilegitpom.xml656133956dae4a2a6f37b475fcf3eddb1659f4291789748402000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comReplace the jTDS JDBC driver by the Microsoft one for SQL Server jTDS isn't maintained anymore since 2013 (1.3.1) whereas the Microsoft JDBC driver is actively supported and tested against the LTS versions of Java. The jre11 artifact is the one to use with Java 11 and higher, hence with the Java 21 required by Silverpeas. 2026-09-18 18:20:02 +0200656133956dae4a2a6f37b475fcf3eddb1659f429Replace the jTDS JDBC driver by the Microsoft one for SQL Servereditpom.xmlgithttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel MoquillonmmoquillonfalseDémarré à distance par l'hôte 140.82.115.31140.82.115.31Started by GitHub push by mmoqui301b3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aeb3a0a7bf423a3407c3bc6980f30a0c6ee678b5aerefs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.git301f002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterf002536b42336ef8b1275d9a17bf9d7aefaff73df002536b42336ef8b1275d9a17bf9d7aefaff73drefs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-dependencies-bom301a099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/mastera099b59d24d9b52a26274503c77c74076a7475f2a099b59d24d9b52a26274503c77c74076a7475f2refs/remotes/origin/masterhttps://github.com/Silverpeas/silverpeas-test-dependencies-bom301c35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterc35c3985f86f4b10ff2dc6b681fce9d45575a3c8c35c3985f86f4b10ff2dc6b681fce9d45575a3c8refs/remotes/origin/masterhttps://github.com/Silverpeas/Silverpeas-Projectbuild.yamlbuild.yamltarget/build.yamlfalse2.0-build2609154067640091Silverpeas_Project_Definition_AutoDeploy 2.0-build260915301false30159674SUCCESS1789482429565https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/301/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/Jenkinsfilesrc/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/Jenkinsfilegitpom.xmlc35c3985f86f4b10ff2dc6b681fce9d45575a3c81789482380000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comManage the tooling generating the documentation of the REST API Smart-Doc is unable to document our REST API in a reliable way: it fails on constructs we rely on, and reports a success while producing an incomplete documentation. Swagger Core replaces it, and produces the OpenAPI specification of the REST services out of both the JAX-RS and the OpenAPI annotations. What doesn't depend on the project is managed here, so that any project documenting its REST API out of a module of its own takes it from this POM: * the plugin of Swagger, its output, the base document carrying the info section that OpenAPI requires and that the plugin has no parameter to fill in, and the binding of its resolve goal to the compile phase -- that goal forks no compilation, so the site lifecycle alone would publish a page without any specification; * RESTEasy among the dependencies of the plugin: its scan by reflection loads the classes of the project, some of them referring types that are otherwise absent from the classpath of the plugin; * the annotations of Swagger, and swagger-core for core-rs to compile the filter completing the responses common to every endpoint and the resolver making the schemas aware of the JAXB annotations; both are declared here as well, core-rs providing them to every project; * the version of Redoc, which renders the documentation; * the execution dropping from the Maven site what isn't that documentation. Only a module declaring the clean plugin inherits it. The executions of the resources and of the dependency plugins are left to the documentation modules, although they are the same in both projects: those two plugins are declared here for every module of every project, which would unpack Redoc into each of their sites. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> 2026-09-15 16:26:20 +0200c35c3985f86f4b10ff2dc6b681fce9d45575a3c8Manage the tooling generating the documentation of the REST APIeditpom.xmlgithttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse302https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/302/300https://integration.silverpeas.org/jenkins/view/Continuous%20Autodeployment%20Build/job/Silverpeas_Project_Definition_AutoDeploy/300/