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

This kata is all about two contributors pushing commits to a shared repository. Given that there's only one of you, you’ll have to do a little role-playing. Starting with this kata, you’ll be playing the part of Ken and Carrie Coder.  

First, we’ll clone the `web-storelist` repository as Ken, then again as Carrie. We’ll then switch back and forth between Ken and Carrie’s local repositories, making commits and pushing them to the Gogs server. We’ll also see how to get commits from a remote repository while updating a local repository.  

Open two terminals using the plus (+) sign:

# Step 1: Clone and configure the repository

In the Ken window below is the command to clone the repository:





cd /home/devops/dk
git clone $EDUCATIVE_LIVE_VM_URL:3000/devops/web-storelist ken.coder

Commands

align-center



This step uses the `git clone` command to retrieve a repository from a remote repository (the Gogs repository). The repository we cloned is the same one we pushed to the Gogs server in the previous kata.  

The entire repository is downloaded from the remote, including the working directory and the index, which includes the entire history of the repository. This is now Ken’s local repository. Ken can make changes in his local repository and push them to the Gogs server. We'll make commits to this repository as Ken.  

The output of this command is:  

Learn about two contributors pushing commits to a shared repository.

Command / Parameter	Description
`cd /home/devops/dk`	This changes to the `dk` directory in the home directory of the current user, `devops`.
`git clone $EDUCATIVE_LIVE_VM_URL:3000/devops/web-storelist ken.coder`	The `git clone` command retrieves a remote repository. The first parameter is `http://ken.coder@localhost:3000/...`. This is the URL to the remote repository. The second parameter is `ken.coder`. This is the directory in which to initialize and download the remote. If the directory doesn't exist, it will be created.

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

Git Kata 7: Collaboration as Ken

Step 1: Clone and configure the repository

Commands