Totally Integrated Automation Portal (TIA Portal) from Siemens is an automation engineering framework that gives users unrestricted access to the complete range of digitalized automation services, from digital planning to integrated engineering and transparent operation. The vendor states users will shorten time to market with the aid of simulation tools, boost the productivity of the plant using additional diagnostic and energy management functions, and increase flexibility via connections to…
N/A
TeamCity
Score 7.3 out of 10
N/A
TeamCity is a continuous integration server from Czeck company JetBrains.
Well suited: It is a software that allows to simulate PID controllers is a valuable educational resource. Users can learn how PID controllers maintain the desired value of a process variable, such as temperature, pressure, or flow, by adjusting system inputs in simulation. It is a program that allows to simulate electro-pneumatic systems can be extremely useful to understand the integration of electronic components with pneumatic actuators, valves, and other elements in automated control systems. Less appropiate: The software appears to be resource intensive in terms of storage and execution. This means that it requires a significant amount of hard disk space and good processing power to run efficiently. On computers with limited or older hardware, the software may run slowly or not be able to execute all of its functions. This is an important limitation for users with limited access to high specification equipment.
TeamCity is very quick and straightforward to get up and running. A new server and a handful of agents could be brought online in easily under an hour. The professional tier is completely free, full-featured, and offers a huge amount of growth potential. TeamCity does exceptionally well in a small-scale business or enterprise setting.
The customization is still fairly complex and is best managed by a dev support team. There is great flexibility, but with flexibility comes responsibility. It isn't always obvious to a developer how to make simple customizations.
Sometimes the process for dealing with errors in the process isn't obvious. Some paths to rerunning steps redo dependencies unnecessarily while other paths that don't are less obvious.
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.
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.
