Skip to content

Jenkins for HMIS

Eric Jahn edited this page Oct 15, 2015 · 6 revisions


Testing and deployment are two integral elements of web development. With some automation mixed in, they become solutions commonly called "continuous integration" (CI) and "continuous deployment" (CD). The "continuous" aspect of these solutions means that your projects will be automatically tested and deployed, allowing you to focus more on writing code and less on herding it onto servers.

What does Jenkins (CI) mean for HMIS

Since HMIS is built on Microservices approach which favors smaller service verses a big monolith. Automating continuous builds and deployment becomes very important. Jenkins provides a perfect automation which allows every team to just focus on their development and design so they can worry less about builds and deployments.

HMIS Jenkins Support

HMIS Jenkins set up performs auto builds up on every check-in to the respective GitHub repository and will also perform auto deployment upon successful execution of the build.Running a build makes sure you don't have compilation errors ,your unit tests passes, your code changes do not impact existing code, your dependencies are configured correctly etc. Additionally we could add code coverage, checkstyle, Find bugs and generating Java docs support if required as part of the build.

HMIS Jenkins Security

Our Jenkins security is Matrix based and hence every user needs to sign up before he/she could see all the projects. Once the user sign up the Jenkins admin provides him appropriate access depending on his role in the project.

HMIS Jenkins Set up

We currently have the following projects configured in Jenkins.

  • HMISService
  • HMISCommon
  • HMISSerialize
  • HMISModel
  • HMISClient
  • Enrollment
  • HMISAuth

But for now the Jenkins URL is Jenkins Jenkins

Clone this wiki locally
You can’t perform that action at this time.