Date: Thu, 28 Mar 2024 10:29:10 +0000 (UTC) Message-ID: <1726482006.361.1711621750617@[3.220.22.64]> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_360_808362825.1711621750614" ------=_Part_360_808362825.1711621750614 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Documentation on a daily build process for map projects in the prod envi= ronment.
The mapping tool contains an admin/daily-build project that is a propose= d mechanism for generating and packaging a daily build as an artifact.
The Release Proce= ssing Tools support generating a release even when map records for a pr= oject are not in a final state. The "process release" mojo will gener= ate RF2 data for any map records that are marked as ready for publication a= nd ignore records that are in process. The basic idea of a daily buil= d is to run this process and then package the resulting data generated into= an artifact that can be pushed up to a maven repository (e.g. Nexus or Arc= hiva).
Looking at the admin/daily-build project, you can see that it is configu= red to call the "perform release" mojo on each of the currently configured = IHTSDO projects (ICD10, ICD9CM, and ICPC). The output directory chose= n for each build is a directory under "target/" so that a later stage can u= se the truezip plugin to package the data as a .zip file and then attach it= as an artifact for this maven module.
At the moment, there is no automation for a daily build. It could be con= figured either as a cron job or as a CI server invocation.
The process can be run manually like this:
cd /home/ihtsd= o/code/admin/daily-build mvn install -PDailyBuild -Drun.config=3D/home/ihtsdo/config/config.properti= es
The output will be three .zip file artifacts for each of the mapping pro= jects that could then be pushed to https://nexus.ihtsdo.org.= p>