| Note | ||
|---|---|---|
| ||
This page represents a working draft. Once it has been finalized, this warning will be removed. |
| Table of Contents |
|---|
Introduction
Example Budget and Timeline
Requirements-Gathering Guidelines
Technical Setup Guide
Continuous Integration and Deployment (CI/CD)
The core OpenLMIS project uses an instance of Jenkins at http://build.openlmis.org to provide continuous integration and delivery (CI/CD). Implementers who wish to do the same are welcome to contact the Core development team via the technical community forum. The forum is actively monitored and Jenkins hosting is a service freely provided to OpenLMIS implementers.
Implementers will find a number of jobs on http://build.openlmis.org upon which they can base their own. Ones such as the OpenLMIS-auth-service are representative of how CI for a typical component may be performed. Meanwhile, the OpenLMIS-3.0-deploy-to-test project is illustrative of how CD 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.
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. OpenLMIS and its constellation of microservices are flexible enough for use with a wide variety of tools and technologies. Nevertheless, implementers may find it convenient to adopt tools such as Jenkins used by the core project.