CI-CD - Install GIT

Git installation instructions: https://git-scm.com/downloads .

GitHub ssh authentication setup documentation:
https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/
https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/


git clone git@github.com:Deepakkachole/cicd-pipeline-train-schedule-jenkins.git

For more information on Jenkins Pipelines, check out the official documentation: https://jenkins.io/doc/book/pipeline/

The basic structure of a Jenkins pipeline consists of stages and steps. You need to be familiar with these concepts in order to build your own Jenkins pipelines.
This lesson discusses these two concepts and walks you through a sample Jenkinsfile that uses a stage and a few steps to implement a CI build.
After completing this lesson, you will be ready to proceed toward implementing more complex functionality within a Jenkins pipeline.

When building Jenkins pipelines, you may need to consult the steps reference: https://jenkins.io/doc/pipeline/steps/

Feel free to check out the sample Jenkinsfile used in the demo for this lesson: https://github.com/linuxacademy/cicd-pipeline-train-schedule-pipelines/blob/example-solution/Jenkinsfile

An important step in the journey toward a full CI/CD Pipeline is containerization. Containers make it easier to implement some of the automation features involved in orchestration. In this lesson, we will discuss what containers are and why we want to use them in the context of a CI/CD Pipeline. We will also introduce Docker, the container tool of choice for this course.

Feel free to check out Docker's own overview of the Docker technology: https://www.docker.com/what-docker