Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Usecase: Source Code Management

Source Code Management

As organizations accelerate delivery, through DevOps, controlling and managing different versions of the application artifacts from code to configuration and from design to deployment is incredibly important. Velocity without robust version control and traceability is like driving a car with out a seatbelt.

Source code management is more than simply tracking changes, versions, and branches of code. Effectively, it includes practices such as:

At GitLab, source code management is a gateway use case to GitLab, where many customers adopt GitLab specifically for SCM. In GitLab, this use case refers to the specific categories Source Code Management and Code Review both under the Source Code Group in the Create stage. Increasingly, this use case is making use of the WebIDE and the Code Snippets categories of the Editor Group and the Wiki and the Design Management categories of the Knowledge Group both under the Create Stage too.

Most of our clients are acquired through the capabilities included in these groups. Given the relevance of this entry point, this page will elaborate on how Source Code Management is used, how our clients solve their problems with these parts of the product and how they leverage these set of features to benefit then from the broader stages of GitLab. Source Code Management is required because software is constantly changing. Regardless of the stage of development, there will be change to deal with. Constantly.

No matter where we are in the system life cycle, the system will change, and the desire to change it will persist throughout the life cycle.

E.H. Bersoff, 1980.

Changes are of different nature:

Change Outcome
Requirements or features may change in scope Business changes
New team members may join Stakeholder changes
Docs are updated all the time Technical changes
Dependencies may have changed Technical changes
The actual code will change! Technical changes

Personas

User Persona

Being the entry point to GitLab means that many user personas find utility and a solution to their problem in Source Code Management. Let's go through the list of power user personas and describe briefly their key motivations to use Source Code Management in GitLab: Parker the Product Manager

Delaney the Development Team Lead

Sasha the Software Developer

Devon the DevOps Engineer

Buyer Personas

Source Code Management purchasing typically do not require executive involvement. It is usually acquired and installed via our freemium offering without producurement or IT's approval. This process is commonly known as shadow IT. When the upgrade is required the VP of IT is the most frequent decision maker. The influence of the VP Application Development is notable too.

Analyst Coverage

Unfortunately, analysts do not cover the Source Code Management market, for several reasons.

Critical Capabilities

TBD

Top 3 Differentiators

Differentiator Value Proof Point
TBD TBD TBD
TBD TBD TBD
TBD TBD TBD

Competitive Comparison

TBD

Customer Case Studies

The adoption of GitLab was quite successful and, within six months, over 1,000 users were active users. Developers explained that the adoption rate was high because GitLab is so easy to use. People actually felt encouraged to contribute code reviews with GitLab Merge Requests. Previous code review tools had 10-20 developers using them, while Worldline currently has 3,000 active users of GitLab - an adoption rate increase of 12,000 percent.

Resources

Presentations

Source Control Videos

Integrations Demo Videos

Clickthrough & Live Demos