Continuous Integration
Testing and deployment are two integral elements of web development. Adding in automation, they become solutions commonly called “continuous integration” (CI) and “continuous deployment” (CD).
URL: http://dev.zana.com:8180Pull requests are a tool for developers to notify the rest of the team when a new feature is completed. This makes everyone aware that they need to revise the code before merging it from the feature branch into the master.
Code merged into master indicates that it is ready for pre-production testing. As such this code is automatically checked for tests and deployed in a development machine
Zana - Dev Machine
At Zana we have the machine dev.zana.com which will be used for the presentation of in-development products. At this machine we will have a Tomcat to deploy services, an elastic search, an apache webserver and an mysql.
Jenkins - the Continous Integration Tool
Jenkins offers a simple way to set up a continuous integration or continuous delivery environment for almost any combination of languages and source code repositories using pipelines, as well as automating other routine development tasks.
Normally Jenkins will retrieve a code from the code repository (e.g bitbucket for Zana), check all the tests automatically and build a war. A script can deploy the war at a local web container (e.g tomcat for Zana)
Jenkins is installed at dev.zana.com:8180
