“Source Code Management –

CS181”
Dr. Kalpna Guleria
Professor, CURIN,
Chitkara University, Punjab
Offered by:
“Department of Computer Science and Engineering,
Chitkara University Institute of Engineering and Technology, Punjab”
“Source Software
“Sourcewith
CodeSource
Management
Code Management
- CS181” - CS181”
 Module 1 st
Git and Version Control

Dr. Kalpna Guleria G01 “Source Code Management - CS181”

 Agenda
Objective - Tools for advanced programming management
We aim to "Explore the Potential" of open source code software
management to provide all a better and more useful platform

Functionality Examination Functionality Utilization

01 Examine the functionality of Software 02 Utilize the functionality of GIT to support
Version Control Systems. version control of source code.

Workflow Analysis Workflow Control

03 Assess workflows in various version 04 Apply the workflows to create
control systems like Git. collaboration with Co Participants

“Source Code Management - CS181”

 KEEP TRACK MODIFICATION WITH

Version
Control System
• Version control systems are software tools
that help software teams manage changes
to source code over time.
• As development environments have
accelerated, version control systems help
software teams work faster and smarter.
USE CASE INTRODUCTI BENIFITS BEST VERSION(s)
ON

Dr. Kalpna Guleria G01“Source Code Management - CS181”

Use Case (Version Control)
Let's say there's a multinational company, that has offices
and employees all around the globe...

Set of Challenges Company Faces

Collaboration Storing Restoring Figuring out the Backup

Versions Previous Version reason behind
“Source Code Management - CS181”
 POSSIBLE SOLUTION
Version Control
System
A version Control system records all the changes made to
a file or set of files, so a specific version may be called
later if needed.

How version control helps high performing

development and DevOps teams prosper
Version control, also known as source control. Version control software keeps track of every modification
Is the practice of tracking and managing changes to software to the code in a special kind of database.
code. If a mistake is made, developers can turn back the clock
Version control systems are software tools that help software and compare earlier versions of the code to help fix the
teams manage changes to source code over time. mistake while minimizing disruption to all team members.
As development environments have accelerated, version Version control protects source code from both catastrophe
control systems help software teams work faster and and the casual degradation of human error and unintended
smarter. consequences.
They are especially useful for DevOps teams since they help Version control helps teams solve these kinds of problems,
them to reduce development time and increase successful tracking every individual change by each contributor and
deployments. helping prevent concurrent work from conflicting.

“Source Code Management - CS181”

 Server
WORKING SENARIO
Version Control Repository

System te it

Update

Commit

U
a

pd
m
pd

Co
A version Control system records all the m

at
U o

e
m
changes made to a file or set of files, so a C

m
it
specific version may be called later if needed.

Working Copy Working Copy Working Copy

Workstation 1 Workstation 2 Workstation 3

“Source Code Management - CS181”

 Benefits of (Version Control)
Using version control software is a best practice for high performing software and DevOps teams. Version control also helps
developers move faster and allows software teams to preserve efficiency and agility as the team scales to include more developers.

Version Control Systems (VCS) have seen great improvements over the past few decades and some are better than
others.
VCS are sometimes known as SCM (Source Code Management) tools or RCS (Revision Control System).
One of the most popular VCS tools in use today is called Git.
 Git is a Distributed VCS, a category known as DVCS, more on that later. Like many of the most popular VCS
systems available today, Git is free and open source.
Regardless of what they are called, or which system is used, the primary benefits you should expect from
version control are as follows.

Branching and
Merging

Traceability Supports
Version Developer's
Comparison Workflow
VCS Benefits

“Source Code Management - CS181”

 Benefits of (Version Control)
Using version control software is a best practice for high performing software and DevOps teams. Version control also
helps developers move faster and allows software teams to preserve efficiency and agility as the team scales to include
more developers.  Version Control Systems (VCS) have seen great improvements over the past few decades and some are better than others.
 VCS are sometimes known as SCM (Source Code Management) tools or RCS (Revision Control System).
 One of the most popular VCS tools in use today is called Git. Git is a Distributed VCS, a category known as DVCS, more on
that later. Like many of the most popular VCS systems available today, Git is free and open source.
 Regardless of what they are called, or which system is used, the primary benefits you should expect from version control are
Branching and as follows.
Merging
Traceability Version
• Creating a "branch" Comparison
Being able to trace each Supports
in VCS tools keeps A complete long-term
change made to the Developer's
multiple streams of change history of Workflow
software and connect it to
work independent every file. Having the annotated
project management and history of the code at
from each other This means every
bug tracking software change made by many your fingertips when
while also providing
such as Jira, and being individuals over the you are reading the
the facility to merge
able to annotate each years. code, trying to
that work back understand what it is
change with a message Changes include the
together, enabling creation and deletion doing and why it is so
describing the purpose and
developers to of files as well as edits designed can enable
intent of the change can
verify that the VCS Benefits to their contents. developers to make
help not only with root cause correct and harmonious
changes on each Different VCS tools
analysis and other forensics. differ on how well they changes that are in
branch do not
conflict. handle renaming and accord with the intended
moving of files. long-term design of the
“Source Code Management - CS181” system.
 Best (Version Control Systems)
Bitbucket
Date launched: 2008
GitHub Owner: Atlassian GitLab
Users: 56 million (as of Sep, 2020)
Owner: GitLab Inc. Nasdaq: GTLB
Founded: 2008
Launched: 2014
Parent organization: Microsoft
Corporation
Perforce
Apache Subversion
Owner: Clearlake Capital, Francisco
Initial release: 20 October 2000
Partners
Developer(s): Apache Software
Founded: 1995
Foundation
License: Apache-2.0 Best
Team Foundation Server VCS Mercurial
Release date: 19 April
Initial release: 2005
2005
Developer(s): Microsoft
License: GPL-2.0-or-later
License: Trialware

Beanstalk
AWS CodeCommit Concurrent Owner: Wildbit
Initial release: July 9, 2015 Version control Founded: 1999 in Philadelphia.
Hosted: Amazon Web Services
Founded: 1986
Developer: FLOSS
community

“Source Code Management - CS181”

“Source Code Management - CS181”
“Source Code Management - CS181”