Gain insights into DevOps by exploring Docker, Git, and Jenkins. Delve into creating CI/CD pipelines, optimizing workflows, and enhancing collaboration through interactive katas and practical exercises.

tarball.tar.gz

nginx

gogs1

gogs2

gogs3

Jenkins

gogs

The course is a collection of DevOps practices and exercises that will teach learners how to use three of the most important DevOps tools: Docker, Git, and Jenkins. Each set of katas will introduce the learners to the tool and its usage. 

The katas build on each other, so that after you're finished, you will have created a complete Continuous Integration/Continuous Delivery pipeline. Through these katas, you will learn to tackle common challenges, optimize workflows, and enhance collaboration between development and operations teams. 

Each katas focuses on specific DevOps practices, enabling readers to gain valuable insights and proficiency in implementing DevOps methodologies effectively. With its interactive approach, the course empowers learners to build a solid foundation in DevOps and foster continuous improvement within their organizations.

DevOps Katas: Mastering DevOps Practices

Jenkins jobs execute build steps. **Build steps** can be general-purpose scripts or custom steps designed for a specific purpose. This kata will show us how to configure the basic steps in a job.  

# Step 1: Add a build step

To execute a build step that writes the build number to a file.

  - Click "Configure." 
  - Click the "Build Steps" tab.  
  - Click "Add build step."  
  - Click "Execute shell."  
  - Enter the following code into the "Command" field:

echo Build ${BUILD_NUMBER} at $(date) > buildlog.txt

Commands

align-center



This script simply appends a new line, including the build number and the current date, to the `buildlog.txt` file in the workspace.  

The "Execute shell" build step is one of the actions that Jenkins can perform as part of a job. The shell build step can execute any shell script, which makes it one of the most flexible available in Jenkins. Custom, purpose-built build steps can be added to Jenkins by installing a plugin, which we’ll see later.  

To run the build:

  - Click "Build Now."  
  - Click "Workspace." 
  - Click `buildlog.txt.` 

Learn about adding a build step and the associated result codes.

Command / Parameter	Description
`echo`	This writes text to standard output.
`Build ${BUILD_NUMBER} at $(date)`	This is the text to write out. `Build` and `at` are text. `${BUILD_NUMBER}`: This is a Jenkins environment variable that's set to the ID of the running build. `$(date)`: This is an environment variable that returns the current date.

Introduction to DevOps

Getting Started With DevOps Katas

Container and Docker

Docker Katas

Source Control Management and Git

Git Katas

Continuous Integration and Jenkins

Jenkins Katas

Mini Project: Git and Jenkins Katas

Conclusion

Appendix

Jenkins Kata 2: Build Steps

Step 1: Add a build step

Commands