Whois & Analysis for gitlab.com

In software engineering, continuous integration (CI) is the practice of merging all developer working copies to a shared mainline several times a day.

Grady Booch first named and proposed CI in his 1991 method, although he did not advocate integrating several times a day.

Extreme programming (XP) adopted the concept of CI and did advocate integrating more than once per day - perhaps as many as tens of times per day.

DevOps (a clipped compound of "software DEVelopment" and "information technology OPerationS") is a term used to refer to a set of practices that emphasize the collaboration and communication of both software developers and information technology (IT) professionals while automating the process of software delivery and infrastructure changes.

It aims at establishing a culture and environment where building, testing, and releasing software can happen rapidly, frequently, and more reliably.

GitLab is a web-based Git repository manager with wiki and issue tracking features, using an open source license, developed by GitLab Inc. The software was written by Dmitriy Zaporozhets and Valery Sizov from Ukraine.

The code is written in Ruby.

Later, some parts have been rewritten in Go.

As of December 2016, the company has 150 team members and more than 1400 open source contributors.

It is used by organisations such as IBM, Sony, Jülich Research Center, NASA, Alibaba, Invincea, O’Reilly Media, Leibniz-Rechenzentrum (LRZ) and CERN.

A component of software configuration management, version control, also known as revision control or source control, is the management of changes to documents, computer programs, large web sites, and other collections of information.

Changes are usually identified by a number or letter code, termed the "revision number", "revision level", or simply "revision".

For example, an initial set of files is "revision 1".

When the first change is made, the resulting set is "revision 2", and so on.

Each revision is associated with a timestamp and the person making the change.

Revisions can be compared, restored, and with some types of files, merged.

In software engineering, a software development methodology (also known as a system development methodology, software development life cycle, software development process, software process) is splitting of software development work into distinct phases (or stages) containing activities with the intent of better planning and management.

It is often considered a subset of the systems development life cycle.

The methodology may include the pre-definition of specific deliverables and artifacts that are created and completed by a project team to develop or maintain an application.