https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/<p>Job to generate and publish the documentation of some of the projects that make the Silverpeas Collaborative platform.</p>
<p>This job should be triggered only the Silverpeas release pipeline.</p>Silverpeas_Documentation_PublishingSilverpeas_Documentation_PublishingSilverpeas_Documentation_PublishingSilverpeas_Documentation_Publishinghttps://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/trueDémarré par le projet amont "Silverpeas_Release" de numéro de build 7373Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.8IMAGEVERSIONPRJ_VERSION3156f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.871159187580Silverpeas_Documentation_Publishing 6.4.831false3164142SUCCESS1790847456246https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/31/- README.md161eebacaec80988e6e8243dacdd2ee7cf726ece1785857382000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comGive a complete info about the project in the README.md file
2026-08-04 17:29:42 +0200161eebacaec80988e6e8243dacdd2ee7cf726eceGive a complete info about the project in the README.md fileeditREADME.md
- src/builds/sso/Jenkinsfile01016743dfe6029fbec83eb133b58304d428f0581785941640000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)
2026-08-05 16:54:00 +020001016743dfe6029fbec83eb133b58304d428f058Update the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)editsrc/builds/sso/Jenkinsfile
- 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/builds/silverpeas/Jenkinsfileeditsrc/releases/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
- src/tests/install/Jenkinsfile56f5661a313b8828cac18f92b68f2f116fbd2cc21789897525000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comQuote the database connection URL passed to setupDB.sh
The URL was interpolated into a shell command without being quoted. As soon as it contains a
semicolon, which is the separator of the parameters in the connection URLs of the Microsoft JDBC
driver for SQL Server, the shell splits the command: the URL is truncated and the remaining
arguments are executed as another command. The URL is now quoted for all the database systems and
for both the creation and the deletion of the database.
2026-09-20 11:45:25 +020056f5661a313b8828cac18f92b68f2f116fbd2cc2Quote the database connection URL passed to setupDB.sheditsrc/tests/install/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse30https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/Démarré par le projet amont "Silverpeas_Release" de numéro de build 7272Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.7IMAGEVERSIONPRJ_VERSION30ee417f2e12a50c898fce7d66542b733c63b400a8ee417f2e12a50c898fce7d66542b733c63b400a8refs/remotes/origin/masteree417f2e12a50c898fce7d66542b733c63b400a8ee417f2e12a50c898fce7d66542b733c63b400a8refs/remotes/origin/masteree417f2e12a50c898fce7d66542b733c63b400a8ee417f2e12a50c898fce7d66542b733c63b400a8refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.770589187580Silverpeas_Documentation_Publishing 6.4.730false3056134SUCCESS1784194266859https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/- src/builds/project-doc/Jenkinsfilec63c56a7332cbacd0b334c0acf871a474aef9eae1777990428000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comWhen updating the parent POM version, do it explicitly without any resolution, in the project of the Web site pusblishing
2026-05-05 16:13:48 +0200c63c56a7332cbacd0b334c0acf871a474aef9eaeWhen updating the parent POM version, do it explicitly without any resolution, in the project of the Web site pusblishingeditsrc/builds/project-doc/Jenkinsfile
- src/releases/silverpeas/Jenkinsfilesrc/builds/mobile/Jenkinsfilesrc/builds/sso/Jenkinsfilesrc/builds/wbe/Jenkinsfilesrc/releases/izpack/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile01d06ccb34ffbca958998fce357470ddc43cbd571778486173000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comIn all Jenkinsfiles, when updating the parent POM version, do it explicitly without any resolution
2026-05-11 09:56:13 +020001d06ccb34ffbca958998fce357470ddc43cbd57In all Jenkinsfiles, when updating the parent POM version, do it explicitly without any resolutioneditsrc/releases/izpack/Jenkinsfileeditsrc/builds/mobile/Jenkinsfileeditsrc/releases/silverpeas/Jenkinsfileeditsrc/builds/sso/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfileeditsrc/builds/wbe/Jenkinsfile
- src/builds/silverpeas/Jenkinsfileee417f2e12a50c898fce7d66542b733c63b400a81781100826000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate pipeline to build a build release of master based upon JEE
2026-06-10 16:13:46 +0200ee417f2e12a50c898fce7d66542b733c63b400a8Update pipeline to build a build release of master based upon JEEeditsrc/builds/silverpeas/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse31https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/31/29https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/29/Démarré par le projet amont "Silverpeas_Release" de numéro de build 7171Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.6IMAGEVERSIONPRJ_VERSION291a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45refs/remotes/origin/master1a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45refs/remotes/origin/master1a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.6420993187580Silverpeas_Documentation_Publishing 6.4.629false2946671SUCCESS1772444551144https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/29/false30https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/28https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/28/Démarré par le projet amont "Silverpeas_Release" de numéro de build 7070Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.5IMAGEVERSIONPRJ_VERSION281a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45refs/remotes/origin/master1a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45refs/remotes/origin/master1a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.573295187580Silverpeas_Documentation_Publishing 6.4.528false2841997SUCCESS1765192393736https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/28/- src/builds/wbe/Jenkinsfile1e65aff8523fd6d2bf304c97d4df2e12036153c01761145033000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the build pipeline for the WebEdition project
2025-10-22 16:57:13 +02001e65aff8523fd6d2bf304c97d4df2e12036153c0Update the build pipeline for the WebEdition projecteditsrc/builds/wbe/Jenkinsfile
- src/builds/silverpeas/Jenkinsfilec0c9295a0e0ce0d5ab0981da18bf062891a165bd1761908307000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comWhen the job for building Silverpeas fails, send an email with the log files generated by wildfly with all the classes loaded in the JVM during the integration tests
2025-10-31 11:58:27 +0100c0c9295a0e0ce0d5ab0981da18bf062891a165bdWhen the job for building Silverpeas fails, send an email with the log files generated by wildfly with all the classes loaded in the JVM during the integration testseditsrc/builds/silverpeas/Jenkinsfile
- src/builds/silverpeas/Jenkinsfile1a4dd1e91ddcba1b9d858bc88f7cabae337d554a1763974390000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comRefine the failure step in the silverpeas build pipeline. Hprof dump is
done of Wildfly and this dump is then sent by email in case of failure.
2025-11-24 09:53:10 +01001a4dd1e91ddcba1b9d858bc88f7cabae337d554aRefine the failure step in the silverpeas build pipeline. Hprof dump iseditsrc/builds/silverpeas/Jenkinsfile
- src/releases/kernel/Jenkinsfilesrc/builds/silverpeas/Jenkinsfile1a3c726bd15b58b1d8b82d9cc1fc5c31a5533a451764000038000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comFix SonarQube Maven execution in pipelines.
In the pipeline dedicated to construct a build version of Silverpeas and
in the pipeline to release a version of Silverpeas,
the execution of the sonarqube analysis fails because the Maven plugin
of SonarQube isn't found. FIx the pb by specifying explicitly the
groupId and artifactId of the SonarQube Maven plugin.
2025-11-24 17:00:38 +01001a3c726bd15b58b1d8b82d9cc1fc5c31a5533a45Fix SonarQube Maven execution in pipelines.editsrc/releases/kernel/Jenkinsfileeditsrc/builds/silverpeas/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse29https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/29/27https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/27/Démarré par le projet amont "Silverpeas_Release" de numéro de build 6969Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.4IMAGEVERSIONPRJ_VERSION270bdaa0f2b228a18722cadfb52fcde86654ecae980bdaa0f2b228a18722cadfb52fcde86654ecae98refs/remotes/origin/master0bdaa0f2b228a18722cadfb52fcde86654ecae980bdaa0f2b228a18722cadfb52fcde86654ecae98refs/remotes/origin/master0bdaa0f2b228a18722cadfb52fcde86654ecae980bdaa0f2b228a18722cadfb52fcde86654ecae98refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.483643187580Silverpeas_Documentation_Publishing 6.4.427false2735630SUCCESS1754577243062https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/27/- src/releases/wbe/Jenkinsfiled51d4c119b9e301c1eba8d136042197d6032c75f1744794321000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the Docker image used to build Silverpeas-WebBrowserEdition
2025-04-16 11:05:21 +0200d51d4c119b9e301c1eba8d136042197d6032c75fUpdate the version of the Docker image used to build Silverpeas-WebBrowserEditioneditsrc/releases/wbe/Jenkinsfile
- src/builds/mobile/Jenkinsfile0bdaa0f2b228a18722cadfb52fcde86654ecae981748850546000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUse of the withCredentials Jenkins statement to allow the injection of
the credentials of the Git account used to push code change into the
Github repo in the AutoDeploy build of the silverpeas mobile project.
2025-06-02 09:49:06 +02000bdaa0f2b228a18722cadfb52fcde86654ecae98Use of the withCredentials Jenkins statement to allow the injection ofeditsrc/builds/mobile/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse28https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/28/blueDémarré par le projet amont "Silverpeas_Release" de numéro de build 6969Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.4IMAGEVERSIONPRJ_VERSION270bdaa0f2b228a18722cadfb52fcde86654ecae980bdaa0f2b228a18722cadfb52fcde86654ecae98refs/remotes/origin/master0bdaa0f2b228a18722cadfb52fcde86654ecae980bdaa0f2b228a18722cadfb52fcde86654ecae98refs/remotes/origin/master0bdaa0f2b228a18722cadfb52fcde86654ecae980bdaa0f2b228a18722cadfb52fcde86654ecae98refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.483643187580Silverpeas_Documentation_Publishing 6.4.427false2735630SUCCESS1754577243062https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/27/- src/releases/wbe/Jenkinsfiled51d4c119b9e301c1eba8d136042197d6032c75f1744794321000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the Docker image used to build Silverpeas-WebBrowserEdition
2025-04-16 11:05:21 +0200d51d4c119b9e301c1eba8d136042197d6032c75fUpdate the version of the Docker image used to build Silverpeas-WebBrowserEditioneditsrc/releases/wbe/Jenkinsfile
- src/builds/mobile/Jenkinsfile0bdaa0f2b228a18722cadfb52fcde86654ecae981748850546000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUse of the withCredentials Jenkins statement to allow the injection of
the credentials of the Git account used to push code change into the
Github repo in the AutoDeploy build of the silverpeas mobile project.
2025-06-02 09:49:06 +02000bdaa0f2b228a18722cadfb52fcde86654ecae98Use of the withCredentials Jenkins statement to allow the injection ofeditsrc/builds/mobile/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse28https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/28/Stabilité du build : Aucun build récent n'a échoué.icon-health-80plushealth-80plus.png100falseDémarré par le projet amont "Silverpeas_Release" de numéro de build 7373Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.8IMAGEVERSIONPRJ_VERSION3156f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.871159187580Silverpeas_Documentation_Publishing 6.4.831false3164142SUCCESS1790847456246https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/31/- README.md161eebacaec80988e6e8243dacdd2ee7cf726ece1785857382000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comGive a complete info about the project in the README.md file
2026-08-04 17:29:42 +0200161eebacaec80988e6e8243dacdd2ee7cf726eceGive a complete info about the project in the README.md fileeditREADME.md
- src/builds/sso/Jenkinsfile01016743dfe6029fbec83eb133b58304d428f0581785941640000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)
2026-08-05 16:54:00 +020001016743dfe6029fbec83eb133b58304d428f058Update the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)editsrc/builds/sso/Jenkinsfile
- 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/builds/silverpeas/Jenkinsfileeditsrc/releases/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
- src/tests/install/Jenkinsfile56f5661a313b8828cac18f92b68f2f116fbd2cc21789897525000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comQuote the database connection URL passed to setupDB.sh
The URL was interpolated into a shell command without being quoted. As soon as it contains a
semicolon, which is the separator of the parameters in the connection URLs of the Microsoft JDBC
driver for SQL Server, the shell splits the command: the URL is truncated and the remaining
arguments are executed as another command. The URL is now quoted for all the database systems and
for both the creation and the deletion of the database.
2026-09-20 11:45:25 +020056f5661a313b8828cac18f92b68f2f116fbd2cc2Quote the database connection URL passed to setupDB.sheditsrc/tests/install/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse30https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/Démarré par le projet amont "Silverpeas_Release" de numéro de build 7373Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.8IMAGEVERSIONPRJ_VERSION3156f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.871159187580Silverpeas_Documentation_Publishing 6.4.831false3164142SUCCESS1790847456246https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/31/- README.md161eebacaec80988e6e8243dacdd2ee7cf726ece1785857382000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comGive a complete info about the project in the README.md file
2026-08-04 17:29:42 +0200161eebacaec80988e6e8243dacdd2ee7cf726eceGive a complete info about the project in the README.md fileeditREADME.md
- src/builds/sso/Jenkinsfile01016743dfe6029fbec83eb133b58304d428f0581785941640000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)
2026-08-05 16:54:00 +020001016743dfe6029fbec83eb133b58304d428f058Update the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)editsrc/builds/sso/Jenkinsfile
- 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/builds/silverpeas/Jenkinsfileeditsrc/releases/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
- src/tests/install/Jenkinsfile56f5661a313b8828cac18f92b68f2f116fbd2cc21789897525000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comQuote the database connection URL passed to setupDB.sh
The URL was interpolated into a shell command without being quoted. As soon as it contains a
semicolon, which is the separator of the parameters in the connection URLs of the Microsoft JDBC
driver for SQL Server, the shell splits the command: the URL is truncated and the remaining
arguments are executed as another command. The URL is now quoted for all the database systems and
for both the creation and the deletion of the database.
2026-09-20 11:45:25 +020056f5661a313b8828cac18f92b68f2f116fbd2cc2Quote the database connection URL passed to setupDB.sheditsrc/tests/install/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse30https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/Démarré par le projet amont "Silverpeas_Release" de numéro de build 7373Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.8IMAGEVERSIONPRJ_VERSION3156f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.871159187580Silverpeas_Documentation_Publishing 6.4.831false3164142SUCCESS1790847456246https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/31/- README.md161eebacaec80988e6e8243dacdd2ee7cf726ece1785857382000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comGive a complete info about the project in the README.md file
2026-08-04 17:29:42 +0200161eebacaec80988e6e8243dacdd2ee7cf726eceGive a complete info about the project in the README.md fileeditREADME.md
- src/builds/sso/Jenkinsfile01016743dfe6029fbec83eb133b58304d428f0581785941640000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)
2026-08-05 16:54:00 +020001016743dfe6029fbec83eb133b58304d428f058Update the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)editsrc/builds/sso/Jenkinsfile
- 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/builds/silverpeas/Jenkinsfileeditsrc/releases/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
- src/tests/install/Jenkinsfile56f5661a313b8828cac18f92b68f2f116fbd2cc21789897525000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comQuote the database connection URL passed to setupDB.sh
The URL was interpolated into a shell command without being quoted. As soon as it contains a
semicolon, which is the separator of the parameters in the connection URLs of the Microsoft JDBC
driver for SQL Server, the shell splits the command: the URL is truncated and the remaining
arguments are executed as another command. The URL is now quoted for all the database systems and
for both the creation and the deletion of the database.
2026-09-20 11:45:25 +020056f5661a313b8828cac18f92b68f2f116fbd2cc2Quote the database connection URL passed to setupDB.sheditsrc/tests/install/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse30https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/Démarré par le projet amont "Silverpeas_Release" de numéro de build 7373Silverpeas_Releasejob/Silverpeas_Release/SILVERPEAS_VERSION6.4.8IMAGEVERSIONPRJ_VERSION3156f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/master56f5661a313b8828cac18f92b68f2f116fbd2cc256f5661a313b8828cac18f92b68f2f116fbd2cc2refs/remotes/origin/masterhttps://github.com/Silverpeas/Jenkins-Pipelines.gitfalse6.4.871159187580Silverpeas_Documentation_Publishing 6.4.831false3164142SUCCESS1790847456246https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/31/- README.md161eebacaec80988e6e8243dacdd2ee7cf726ece1785857382000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comGive a complete info about the project in the README.md file
2026-08-04 17:29:42 +0200161eebacaec80988e6e8243dacdd2ee7cf726eceGive a complete info about the project in the README.md fileeditREADME.md
- src/builds/sso/Jenkinsfile01016743dfe6029fbec83eb133b58304d428f0581785941640000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comUpdate the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)
2026-08-05 16:54:00 +020001016743dfe6029fbec83eb133b58304d428f058Update the version of the silverbuild Docker image to use for constructing a build version of the Silverpeas-Sso project: now it uses the latest version of silverbuild (with Java 17 and Wildfly 34)editsrc/builds/sso/Jenkinsfile
- 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/builds/silverpeas/Jenkinsfileeditsrc/releases/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
- src/tests/install/Jenkinsfile56f5661a313b8828cac18f92b68f2f116fbd2cc21789897525000https://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonmiguel.moquillon@silverpeas.comQuote the database connection URL passed to setupDB.sh
The URL was interpolated into a shell command without being quoted. As soon as it contains a
semicolon, which is the separator of the parameters in the connection URLs of the Microsoft JDBC
driver for SQL Server, the shell splits the command: the URL is truncated and the remaining
arguments are executed as another command. The URL is now quoted for all the database systems and
for both the creation and the deletion of the database.
2026-09-20 11:45:25 +020056f5661a313b8828cac18f92b68f2f116fbd2cc2Quote the database connection URL passed to setupDB.sheditsrc/tests/install/Jenkinsfile
githttps://integration.silverpeas.org/jenkins/user/mmoquillonMiguel Moquillonfalse30https://integration.silverpeas.org/jenkins/view/all/job/Silverpeas_Documentation_Publishing/30/32SILVERPEAS_VERSIONthe version of Silverpeas for which the documentation will be generatedSILVERPEAS_VERSIONStringParameterDefinitionIMAGEThe version of the Docker image used to build SilverpeasIMAGEStringParameterDefinitionVERSIONA version of Silverpeas for which the documentation has to be generated and then publishedVERSIONStringParameterDefinitionPRJ_VERSIONThe version of the Silverpeas global project definition in which are defined a lot of information about Silverpeas as well as the common required dependencies to build a Silverpeas project.PRJ_VERSIONStringParameterDefinitiontruefalsefalsefalse