This page represents a working draft. Once it has been finalized, this warning will be removed. |
The OpenLMIS project uses an instance of Jenkins at http://build.openlmis.org to provide continuous integration and delivery (CI/CD).
Implementers will find a number of jobs on http://build.openlmis.org upon which they can base their own. Because of the micro-services nature of OpenLMIS, each service/component has a Jenkins build job. For example, a job such as the OpenLMIS-auth-service is representative of how CI for a typical component may be performed. Meanwhile, there are also deployment pipelines to update each server environment with a specific build version or snapshot of a set of components. For example, a job such as OpenLMIS-3.0-deploy-to-test is illustrative of how this CD pipeline may be achieved.
More information about Jenkins can be found here. Meanwhile, detail about the Core project’s use of it is available in its documentation. (The link above is another place...maybe we need to group the set of relevant links and explain what each link covers.)
As described here, the core OpenLMIS project makes extensive use of continuous integration and delivery (CI/CD) to help ensure its quality. Implementers are highly encouraged to do the same.