GitLab is a complete open-source DevOps platform, delivered as a single application, fundamentally changing the way Development, Security, and Ops teams collaborate and build software. From idea to production, GitLab helps teams improve cycle time from weeks to minutes, reduce development process costs and decrease time to market while increasing developer productivity.
$0
per user per month
TeamCity
Score 8.2 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
N/A
Pricing
GitLab
TeamCity
Editions & Modules
Free
$0
per user per month
Free
$0
per user per month
SaaS Premium
$19
per user per month
Premium
$19
per user per month
SaaS Ultimate
$99
per user per month
Ultimate
$99
per user per month
No answers on this topic
Offerings
Pricing Offerings
GitLab
TeamCity
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
We provide free Gold and Ultimate licenses to qualifying open source projects and educational institutions, find out more by visiting our pricing page.
So far, we can say that Gitlab improves the way in which we work. We set some conventions and stick to them in all the projects. We love that the repository integrates so well into the complete CI/CD solution.
This application is easy to install and deploy at site than most of the similar solutions in market. Easy user interface is one of the reason it can be installed. However each software have its good points and bad points. Study your organizations case and then only choose …
I would also like to compare TeamCity against Snap-Ci as well as Concourse. We chose TeamCity over all of these tools because of its ability to be set up easily against a restricting corporate firewall. We needed to integrate unit tests, integration tests, pushes to production, …
Initial team collaboration was very difficult before the Gitlab integration. There is no code version maintained by the developer leading to problematic situations when actual deployment needs to be done. The initial setup was a learning curve, but the overall integration helped to work with the team. The CI/CD pipeline also helped to easy deployment.
TeamCity is well suited for an organization using continuous integration, meaning you release code to production often, and an agile project management system. There are free versions available for small teams and enterprise versions available for large teams with many different builds. TeamCity is probably overkill for basic e-commerce or blog website builds that do not require much development after the initial launch
The way they have managed to provide the version management aspect using git with project setup and users is mesmerising cause there's no product out there that gives this freely.
Continuous updates and hearing what users need is what the product engineers at GitLab are doing best. They come back to you with exactly what you need every while.
Quality features, Latest tech integrations have made the end-to-end solution very flexible and agile.
CI/CD tools implementation with pipelines and deployment strategies is just making the job for Infra teams smoother.
Fully customizable build process. Each step of the build process can be parameterized and customized to address specific needs of particular applications. This allowed us to easily convert from a custom VM-based environment to our current Docker-based environment.
Manages large numbers of build agents seamlessly. This allows us to run multiple builds on many different applications in a most efficient manner.
Build steps can be managed in an arbitrary manner, allowing some parts of the process to proceed in parallel while restricting others to depend on completion of all relevant steps.
Documentation of CI features have room for improvement, in particular in cases where own runners with pre-deployed images are used
Project management features, such as milestones etc. seem un-intuitive, and we struggle to get developers to actually use them
Settings for having GitLab send email notifications ought to be more fine-grained. Seems like it is a choice between emails for everything, and no emails at all
Gitlab is the best in its segment. They have a free version, they have open-source software, they provide a good service with their SaaS product, they are a fully-remote company since the beginning (which means they are fully distributed and have forward-thinking IMO). I would certainly recommend them to everyone.
The web console management is superior and I would have given Gitlab a 10, but sometimes it is hard to find documentation about a configuration setting in the gitlab.rb configuration file. As we move everything to code that means moving our CVS tools to code as well - and Gitlab to code. The usability of Gitlab from the end user's perspective is superior and the usability from the operations team is very good and getting better but there could be a little improvement in the gitlab.rb config file layout and documentation.
TeamCity runs really well, even when sharing a small instance with other applications. The user interface adequately conveys important information without being overly bloated, and it is snappy. There isn't any significant overhead to build agents or unit test runners that we have measured.
At this point, I do not have much experience with Gitlab support as I have never had to engage them. They have documentation that is helpful, not quite as extensive as other documentation, but helpful nonetheless. They also seem to be relatively responsive on social media platforms (twitter) and really thrived when GitHub was acquired by Microsoft
We have a small custom code development group. We only needed a basic entry-level code management repository. Gitlab meets our needs and is very price advantageous compared to others on the market. We also needed a system that is easy to administer and easy to grant access to our limited-size user base. Gitlab does what we need and gives the necessary flexibility for application support, user administration, and code/version control needs to be required.
TeamCity is a great on-premise Continuous Integration tool. Visual Studio Team Services (VSTS) is a hosted SAAS application in Microsoft's Cloud. VSTS is a Source Code Repository, Build and Release System, and Agile Project Management Platform - whereas TeamCity is a Build and Release System only. TeamCity's interface is easier to use than VSTS, and neither have a great deployment pipeline solution. But VSTS's natural integration with Microsoft products, Microsoft's Cloud, Integration with Azure Active Directory, and free, private, Source Code repository - offer additional features and capabilities not available with Team City alone.
TeamCity has greatly improved team efficiency by streamlining our production and pre-production pipelines. We moved to TeamCity after seeing other teams have more success with it than we had with other tools.
TeamCity has helped the reliability of our product by easily allowing us to integrate unit testing, as well as full integration testing. This was not possible with other tools given our corporate firewall.
TeamCity's ability to include Docker containers in the pipeline steps has been crucial in improving our efficiency and reliability.
