TeamCity 4.0 released
What is TeamCity? TeamCity is, in scientific terms, an integrated environment that increases the efficiency of group development, taking on such routine actions as building builds, running and analyzing tests, as well as analyzing the source code (inspections, searching for duplicates, etc.). ) Looking at the picture, many things will become clear:
For the first time, I encountered TeamCity about six months ago and now use it every single day of God. I do not want to arrange a marketing presentation from the post (all this can be read / viewed here ), but I just want to list the things that really help me in my daily work.
1. Unit testing.
If you are a Team or Tech Leader in a project, then, probably, the phrase “Vasya, why did you commit the code without running the tests before that ?? Now the Mashkin component is crookedly working !!! ”is very familiar to you. How to force developers to run unit tests? Can do it by force? :) Depending on the configuration and settings, TeamCity can follow developer commitments and immediately start building a build, and after that, unit tests. If, after Vasin kommit, there are new dropped tests, then Vasya will receive a letter from the system that it would be nice to see if this is his fault? Same as if compilation fell after Vasin kommit.
TeamCity has a web-interface and you can watch what is happening and in real time.
')
2. You can use multiple version control systems. For example, in my project Perforce and SVN are used simultaneously.
3. Code Review by Inspections and Finding Duplicates
The analysis (Java code) is based on IntelliJ IDEA inspections, and there are more than 600 of them. As a result, the person responsible for the quality of the code can quickly respond to the bullsh * t that Vasya takes and tactfully hint about it.
Finding duplicates is also a very useful thing. After all, developers are often in a hurry " tyryat " from each other's code, instead of somehow transforming it or putting it into a common place. Or they simply think, “Now save and paste, and then I will rewrite everything,” and then they forget. In TeamCity, all this can be easily viewed.
4. Remote Run
This is such a convenient feature. Instead of a commit you do Remote Run. If the compilation and all tests have passed, then the samples will be committed.
In general, I advise you to play around, especially if you are writing large applications in Java. Unfortunately, I did not work with TeamCity under .NET, so they will not say anything. Let others sign off.
For the first time, I encountered TeamCity about six months ago and now use it every single day of God. I do not want to arrange a marketing presentation from the post (all this can be read / viewed here ), but I just want to list the things that really help me in my daily work.
1. Unit testing.
If you are a Team or Tech Leader in a project, then, probably, the phrase “Vasya, why did you commit the code without running the tests before that ?? Now the Mashkin component is crookedly working !!! ”is very familiar to you. How to force developers to run unit tests? Can do it by force? :) Depending on the configuration and settings, TeamCity can follow developer commitments and immediately start building a build, and after that, unit tests. If, after Vasin kommit, there are new dropped tests, then Vasya will receive a letter from the system that it would be nice to see if this is his fault? Same as if compilation fell after Vasin kommit.
TeamCity has a web-interface and you can watch what is happening and in real time.
')
2. You can use multiple version control systems. For example, in my project Perforce and SVN are used simultaneously.
3. Code Review by Inspections and Finding Duplicates
The analysis (Java code) is based on IntelliJ IDEA inspections, and there are more than 600 of them. As a result, the person responsible for the quality of the code can quickly respond to the bullsh * t that Vasya takes and tactfully hint about it.
Finding duplicates is also a very useful thing. After all, developers are often in a hurry " tyryat " from each other's code, instead of somehow transforming it or putting it into a common place. Or they simply think, “Now save and paste, and then I will rewrite everything,” and then they forget. In TeamCity, all this can be easily viewed.
4. Remote Run
This is such a convenient feature. Instead of a commit you do Remote Run. If the compilation and all tests have passed, then the samples will be committed.
In general, I advise you to play around, especially if you are writing large applications in Java. Unfortunately, I did not work with TeamCity under .NET, so they will not say anything. Let others sign off.
Source: https://habr.com/ru/post/45740/
All Articles