There is sometimes a need to define a common build step in a template, so that this step will be executed either before all build configuration steps or after them. Here’s a simple example. I’m building a lot of typical Maven projects, and for most of the part their build is the same: just run mvn clean package and upload the binaries to the maven repository. However, for some of the builds, I need the additional steps to run in between mvn package and mvn deploy. In TeamCity, the requirement above can be implemented with the aid of Build Configuration Templates. Starting with version 20

Enforcing some rules in a project might be quite useful to keep the things in order. For instance, enforce agent side checkout everywhere, or make sure that all build configurations have some strict execution timeout, or enable build files cleanup (Swabra) for all the builds. Starting with 2018.1, TeamCity provides the ability to enforce settings for all of the build configurations in a project hierarchy. To enforce some settings in the project hierarchy, a template with these settings must be created. After that, a system administrator can set this template as the enforced settings temp

While more new features are introduced to PyCharm 2.0, the older ones are also being developed — namely Django template debugger, which first appeared in version 1.5. Now I would like to promote it one more time in order to ask for some feedback for a future development or just inform those who didn't know about it yet. How to use the template debugger? Very simple! Just place a breakpoint in your template file at a line with any Django tag or expression. Run Django server in Debug mode (Shift+F9) and make it render the template (e.g. open the page in your browser). Voilà! The se

It's quite a typical case when you need to create several more or less similar build configurations in TeamCity, for example, to run builds in different environments, or create a separate build configuration for release builds, etc. Of course, you can simply copy build configurations, but what if you'll need to change, for example, a VCS root in all of them? Naturally, you'll have to manually change it in every configuration. Don't you think it's too much of routine work? We thought so too, that's why in TeamCity there are build configuration templates. You can create a template with common (s