Gitlab: a git based CI/CD platform

Item: GitLab
Rating: 9
Author: Dhruba Jyoti Nag

Overall Satisfaction with Gitlab

Use Cases and Deployment Scope

Gitlab is used by all departments at my current client as a code repository and a tool for automated integration and deployment. It is used across the IT department. It has been used to implement the CI/CD system and source control. It has also been used for tagging. It has different runners which run different tasks.

Pros and Cons

Pros

CI/CD implementation
Source control
User access of the source code

Cons

Runner performance
Real-time job and task status
Nested pipelines

Return on Investment

Runners/tasks for CI/CD. Once the jobs/tasks are set up, they can be easily executed by the operations team.
Inexpensive source control
It can be configured to push code to the container in AWS.

Alternatives Considered

The competitor of Gitlab would be Github or other git based implementations. It is a comparatively new space introduced after the inception of the revolutionary git. Gitlab fares quite well in this space in comparison to its competitors. It has a host of enterprise features including CI/CD which has made it a very tempting choice over time.

Other Software Used

Postman, Logstash, Elasticsearch

Likelihood to Recommend

Gitlab does a wonderful job when it comes to implementing CI/CD in a project. Once tasks are set up, they can be used by developers to push code in production making it a really easy tool for day to day operations. It also has amazing source control features which are not just limited to code storage, but teams and individuals can access the code repositories.

Comments

Please log in to join the conversation