Integrating the repository with different environments of software production to synchronize the workflow.
Continuous integration is a coding philosophy and set of practices that drive development teams to implement small changes and check in code to version control repositories frequently. Because most modern applications require developing code in different platforms and tools, the team needs a mechanism to integrate and validate its changes.
Here we will use Docker, Git-hooks and Jenkins to showcase a sample DevOps pipeline.
If Developer push to dev branch then Jenkins will fetch from dev and deploy on dev-docker environment.
If Developer push to master branch then Jenkins will fetch from master and deploy on master-docker environment.
PS: both dev-docker and master-docker environment are on different docker containers.
Jenkins will check (test) for the website running in dev-docker environment. If it is running fine then Jenkins will merge the dev branch to master branch and trigger #job 2 For this we need to add two things:
- First
if sudo curl IP-Of-Dev-Envis true we can proceed with merging. - Add a post build trigger in Jenkins for building #Job2
You are always welcome to add more or improve any resource in this repository by following these instructions.