DevOps CD Automation : Git -> Jenkins -> Docker

6
DEVOPS – CONTINUOUS DEPLOYMENT AUTOMATION GIT -> JENKINS -> DOCKER

Transcript of DevOps CD Automation : Git -> Jenkins -> Docker

Page 1: DevOps CD Automation :   Git  -> Jenkins -> Docker

DEVOPS – CONTINUOUS DEPLOYMENT AUTOMATION

GIT -> JENKINS -> DOCKER

Page 2: DevOps CD Automation :   Git  -> Jenkins -> Docker

Continuous Testing

Continuous Deployment

Continuous Monitoring

DevOps

Continuous Integration

Continuous Development

Continuous Feedback

Page 3: DevOps CD Automation :   Git  -> Jenkins -> Docker

GIT -> Create a Git repository ->

Create a Dockerfile (- to build a container for a php web application shown above in video as an example) inside the Git repository ->

Create other components (index.php under src folder in above example) in the git repository needed to run the designated application inside a docker container -> Change one of these components to git commit the change and trigger a Jenkins build ->

Page 4: DevOps CD Automation :   Git  -> Jenkins -> Docker

GIT -> JENKINSCreate a Jenkins freestyle project in Jenkins -> Update the above created Git repository location under SCM configuration of the project -> Select trigger builds remotely and input an authorization token in the configuration ->

Update .git/hooks/post-commit file with a syntax to trigger the Jenkins job created in above step -> Update .git/hooks/post-commit file with a syntax to execute docker commands to create and run a docker container using a Dockerfile->

Page 5: DevOps CD Automation :   Git  -> Jenkins -> Docker

JENKINS -> DOCKERDocker commands can be put in an executable file (buildExecutable in this case) ->

Commit the change made (- in one of above steps) in application component -> post-commit of .git/hooks folder will trigger the Jenkins build job ->post-commit will also execute docker commands to build and run a docker container running an application within (a php web application in this case).