Scalable and simple to use with lots of very good plug-ins
What is our primary use case?
For my company, we require a CI server that's very flexible. Our bills are simple, almost template-based, however, we need to be able to deploy to almost any platform, basically whatever the customer could end up using, whether it be Windows, Mac, Android, and even mobile or tablets, et cetera. We can do it with this solution. It needs to be simple because right now as I am the only IT person knowledgable of infrastructure on the team. If we need to build a pipeline, it needs to be simple enough that the rest of the team would be able to understand and work with it.
Pros and Cons
"TeamCity is very useful due to the fact that it has a strong plug-in system."
"If TeamCity could create more out of the box solutions to make it more user friendly and create more use cases, that would be ideal."
What other advice do I have?
We're just a customer. We're using the most up to date version of the solution currently. TeamCity is our main continuous integration tool, however, it is deployments that we were looking into improving. With Harness I saw that the deployment process was very polished. And at this point I was wondering if there was any interactivity between the two solutions, or just what would be the benefits of just switching completely to Harness. We're currently researching that now. I'd advise other organizations to do a lot of research before you begin creating anything. The solution needs a lot of…