- Centralized build automation
- Ability to embed powershell scripts for automated deployments
- Auditability of builds
- Unit tests
- Smoke tests
- Automated deployments
Continuous integration has reduced build failures and highlighted issues sooner. Automated deployments of web services, database scripts and applications chained across all environments has minimized time and effort, sped up delivery time, reduced risk of human error and enabled automated communication to stakeholders via integration with JIRA for release notes.
I've used it for three years.
Occasionally issues deploying software using the tool due to configuration issues within the tool (mostly around powershell configuration).
We had to add additional servers to enable a failover capability, but this was more to do with our infrastructure
No issues enquired.
I've not required customer service.Technical Support:
It's good. It's done via online forums.
We previously used Jenkins and Cruise control. We changed to enable one common solution and standard support model, also better functionality.
It was very simple. I have also installed on my home server to enable me to continue to develop and learn the tool.
We did it in-house.
The initial cost was only the cost of a virtual server, and database which was less than 1000 Euros a month. I am not aware of ongoing costs.
No other options were evaluated.
Make sure you define the standards and naming conventions prior to implementing TeamCity.