Overview
Documentation on a daily build process for maps.
Details
The mapping tool contains an admin/daily-build project that is a proposed mechanism for generating and packaging a daily build as an artifact.
The Release Processing Tools support generating a release even when map records for a project are not in a final state. The "process release" mojo will generate RF2 data for any map records that are marked as ready for publication and ignore records that are in process. The basic idea of a daily build 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 Archiva).
Looking at the admin/daily-build project, you can see that it is configured to call the "perform release" mojo on each of the currently configured IHTSDO projects (ICD10, ICD9CM, and ICPC). The output directory chosen for each build is a directory under "target/" so that a later stage can use the truezip plugin to package the data as a .zip file and then attach it as an artifact for this maven module.
Now, to enable this, some CI or cron automation would be needed to invoke a "mvn install" on this very project and it would produce three .zip artifacts that could then be added to a corresponding repository and daily build data would then be available to any users of that repository.
cd /home/ihtsdo/code/admin/daily-build mvn install -PDailyBuild -Drun.config=/home/ihtsdo/config/config.properties
References/Links
- n/a