German company SUSE offers SUSE Manager, a software defined infrastructure Linux server configuration management tool supporting patching, provisioning of Linux servers, and related actions.
N/A
TeamCity
Score 7.4 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
We used the open source components of SUSE Manager before which helped - but SUSE Manager merged them together and made working with the tools a lot easier.
I have tested and evaluated Uyuni, which is basically the upstream version of SUSE Manager. We opted for SUSE Manager because we like to have a stable release that is regularly updated and has full support from our vendor.
It's a very convenient way of tracking, monitoring, and auditing reports on our databases. Reduces runtime, complexity to manage IT operations. Meets all security and compliance standards. Great support.
The other competitors also have a good platform and service, but we went with SUSE due to cost. The price was best and we needed to keep under a certain budget. The functionality was perfect for what we needed so we took the step forward. This allows us to manage our Linux …
I tested Ansible as well, but the product doesn't really compare to SUSE Manager. Ansible is basically defining states for your systems and pushing them. SUSE Manager is a complete one-stop shop for everything a system administrator wants to do to effectively manage their …
Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find …
Since we were already making use of other JetBrains offerings, TeamCity had a leg up on the competition due to the ease of integration with these tools. With that said, TeamCity's feature set stacks up well with the competition. Jenkins definitely has some nice features, but …
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, …
TeamCity competes against the TFS build, Visual Studio Team services and Jenkins the open source workhorse. The reason for selecting TeamCity was because it was found to be a great fit for all the diverse projects on a spectrum of technologies we have which the TFS Build …
Cloud Services Practice Manager and Principal Architect
Chose TeamCity
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 …
I like the quality of Jetbrains products. TeamCity is well supported and regularly updated by Jetbrains. They have an active support forum and most questions are answered quickly.
TeamCity is very extendable and has been able to handle everything we've been required to do.
We've only ever really used TeamCity as a CI platform. Running tests on these CI clusters is worlds more efficient and just plain easier than having to run individual tests on your local machine. You just hit one button here, versus either writing some run script or even worse …
TeamCity is the best combination of price and full features. It has a good web UI and doesn't need a lot of manual configuration files, but it still is incredibly extensible and can do just about any build or release task you set it at. If it can't do it, the odds are it has a …
Jenkins and Team Foundation Server (TFS) are both strong products. Compared to Jenkins, TeamCity is much more mature and polished. Though Jenkins is open-source/free, the cost of TeamCity is a drop in the bucket compared to the total cost of even one project we're using it …
In our specific use case, SUSE Manager is extremely useful. We're having a large landscape that is divided into intake, development, quality and production with a couple of different SUSE flavours that need to be automatically rolled out, configured, patched and maintained, everything from up to date repositories that are cloned on a daily basis straight from SUSE.
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
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.
The gui is extremely user friendly. The installation and configuration does have a learning curve, it takes a while to set everything up. But once you're passed this initial learning curve, everything is very intuitive. If you want extra automation, there's an api (eventough i personally find the documentation of the api could be ordered better). I gave this product a 9 because of the initial learning curve and the api documentation, but for the rest it suits my needs perfectly.
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.
SUSE Manager provided a top-tier support person on site to us for two days to help integration. We did all the standard stuff they help with before he arrived. We were able to use him to get all the tricky stuff identified and solved in the short time we had. Had they sent us a lower-tier guy, it would have been a waste. I was impressed they sent such knowledgeable person.
The other competitors also have a good platform and service, but we went with SUSE due to cost. The price was best and we needed to keep under a certain budget. The functionality was perfect for what we needed so we took the step forward. This allows us to manage our Linux environment within the manager and update or deploy specific tasks to each as needed.
Jenkins relies on being open source as the primary driver for its success. This low cost is a huge factor for many companies, both small and large. The professional, free tier of TeamCity offers a huge amount of growth before ever needing to pay anything. I personally also find the user experience of TeamCity to be much better, both from a look and feel, as well as from an out-of-the-box feature set perspective. The big selling feature of ADO is its native integration with Azure. TeamCity integrates very well with out-of-the-box .NET support and greatly simplifies our use of another diverse tooling outside of the Microsoft ecosystem.
TeamCity was a key contributor to our organization's adoption of Agile.
TeamCity made it possible to KILL "It works on my laptop" conversations with Developers. If it does not compile in TeamCity - the project is not deployable. TeamCity's easy to use interface made it possible to quickly adopt a "Deploy Only from TeamCity" policy, further ensuring TeamCity Builds were the gold-standard for well-configured source code.