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

# Workflow

A developer **workflow** is a set of steps required to accomplish a particular task. There are workflows for adding new code to a codebase, testing, code reviews, and other tasks. Managing work in an #key# SCM: source control management #key# system is one of several workflows.

Git supports a number of common workflows. One Git workflow, based on branching, is called a **feature branch workflow**. A typical day in the life of a developer using a feature branch workflow might look like the following:  

A developer arrives at work, starting their day, and then they:  

1. Open a task list, such as a kanban board.

2. Pull a task off the list to complete.

3. Update their local repository with work committed to the authoritative repository by other developers.

4. Create a **local feature branch** (also called a **topic branch**) and switch their local repository to that new branch.

5. Write the code to complete the feature specified in the task and commit that work to the feature branch.

6. Upload the feature branch to the authoritative repository when the task is complete.

7. Submit a request (called a **pull request**) through the authoritative repository system to have their code merged into the main branch.

8. Start over from Step 2 with a new unfinished task while waiting for their request to be processed. 

Learn about Git's workflows, tools, and uses.

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 Workflows, Tools, and Uses

Workflow