Gitlab. Perfect for CI
Updated September 22, 2020

Gitlab. Perfect for CI

Marco Carnevali | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Gitlab

We use Gitlab for every code project we have such as the website, APIs and mobile applications. It offers a free plan that has everything you need. We use Gitlab, especially for it's CI (continuous integration) feature that let us automate team working and deploying frameworks on dev and productions channels
  • Continuous integration
  • Git
  • Automations
  • Artifacts
Gitlab is far better for its continuous integration. It gives you pre-made scripts to build and send an artifact to you or your team.
We haven't use any security features provided by gitlab
We use continuous integration to share artifacts and developing status across all our channels including slack. It helps automate the QA process and get things done quicker.
I've never used Gitlab support.

Do you think GitLab delivers good value for the price?

Yes

Are you happy with GitLab's feature set?

Yes

Did GitLab live up to sales and marketing promises?

Yes

Did implementation of GitLab go as expected?

Yes

Would you buy GitLab again?

Yes

Bitbucket, GitHub, Microsoft 365 (formerly Office 365)
Gitlab it's needed if you are developing software, and you want to enhance your development with integrations and automation.

Collaboration and Performance

Yes we use gitlab to store more than 10 different code projects. Thanks to CI we enabled automations to connect Gitlab to third party services like Slack and really helped team collaborating.
We use gitlab issue and Pull requests to assign bug or features request to developers on our team and to merge code from different environments
We replaced bitbucket just because gitlab let us have more and better automations using CIs

Using Gitlab

5 - They represent the core business. We store the website, mobile applications and API of all our products
2 - Supporting gitlab it's really easy you just need to know how to use any Git service and dev-ops softwares
  • Automations
  • Artifacts
  • Store code
  • Integrating gitlab with third party services
  • for testing the backend in an automated way
We haven't found a service as good as gitlab on the CIs level

Evaluating Gitlab and Competitors

Yes - It replaced bitbucket for dev-ops. We replaced it because gitlab is far better on the CI department and it help us automating and deploying artifacts in a quicker and easier way then bitbucket
  • Product Features
  • Product Usability
  • Product Reputation
  • Prior Experience with the Product
We decided to use Gitlab for price + automations and CIs features the gitlab provides
in the process I would evaluate "Gitlab" just because it now supports CIs

Gitlab Support

ProsCons
No escalation required
Immediate help available
Slow Initial Response
During setup process I couldn't implement a edge feature of CI and they helped me indicating what tutorial to follow

Using Gitlab

ProsCons
Like to use
Relatively simple
Easy to use
Technical support not required
Well integrated
Consistent
Feel confident using
None
  • Continuos integration
  • Managing projects
I think gitlab is really easy to use but they still have way to improve the UX of their interface