Scribd
Upload
12 views11 pages

Dev Ops

Class Lecture on Devops by Prof Mayank Vatsa, IIT Jodhpur

Uploaded by

h725c89ffv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
12 views11 pages

Dev Ops

Class Lecture on Devops by Prof Mayank Vatsa, IIT Jodhpur

Uploaded by

h725c89ffv
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 11

DevOps

Slides prepared from many sources


What is DevOps?

• Patrick Debois, who’s often called “the father of DevOps”, coined the
word “DevOps” in 2009.
What is DevOps?
• DevOps is an approach based on agile and lean principles in which business
owners, development, operations, and quality assurance team collaborate to
deliver software in a continuous stable manner

• DevOps is an environment that promotes cross practicality, shared business


tasks and belief

• DevOps is a movement that improves IT service delivery agility

• DevOps is a culture that promotes better working relationship within the


company

• DevOps is a set of practices that provides rapid, reliable software delivery


What is DevOps?
DevOps Tools
One of the popular tool is Git

• Git is a DevOps tool used for source code management.

• It is one of the most prominent version control systems (VCS) today that is
widely used to handle small and large projects e ciently.

• It helps in tracking changes in source code, enabling di erent people to


collaborate on di erent parts of the same program.
ff
ffi
ff
Version Control
Git
• Git is a distributed version control system for tracking changes.
• It helps in coordinating work amongst several people in a project and tracks progress
over time.

• Unlike the centralized version control system, Git branches can be easily merged.
• A new branch is created every time a developer wants to start working on something.
This ensures that the master branch always has a production-quality code.

• Every developer gets their local repository with full commit history.
• The commit history makes Git fast, as now a network connection is not needed to
create commits or perform di s between commits.
ff
Git Branching
• Any code in the main branch should be
deployable.
• Create new descriptively named branches off the
main branch for new work, such as feature/add-
new-payment-types.
• Commit new work to your local branches and
regularly push work to the remote.
• To request feedback or help, or when you think
your work is ready to merge into the main branch,
open a pull request.
• After your work or feature has been reviewed and
approved, it can be merged into the main branch.
• Once your work has been merged into the main
branch, it should be deployed immediately.
Git vs Github
• Git con g
• Git init
• Git add
• Git diff
• Git commit
• Git reset
• Web interface
• Git status
• Git merge
• Git push
• Git pull
fi
GitHub - how to use

You might also like