EAP 10455 Feedback

Alex,

We are comfortable in any format of discussion. You can describe general comments  here. If you have a list of concrete issues feel free to post them in out issue tracker.

Hi,

first part of the feedback:

I love the "Administration > Audit" feature.
It's great to see the list of all configuration/administration changes in case you have a group of TeamCity admins. This can help a lot to reduve the maintenance overhead in case of problems.

--a.

Hi folks,

my feedback about the build configuration templates feature: Its nice to have templates, but the current implementation is not sufficient for our major use case.

Our major use of template is a build project template with a common set of configured build configurations -- for which beside some property values the vcs roots can be changed, too.
Most of our projects are related to a specific branch, for instance for a release branch. Currently, for the creation of a new release branch, we copy a build project for an old one and re-configure the project such that it uses the new release branch. However, we are missing a build change to change some properties of all related release branch builds.

Hence we are missing

• build project templates
• the ability to exchange the vcs root of a build configuration which is linked to a template.

Regards,
Alex

In fact you can use references to configuration parameters in checkout rules. So if you are using Subversion you can define VCS root for the whole repository and checkout necessary parts (branch or trunk) with help of checkout rules which in turn can be defined via parameters. Values of these parameters can be different in all template based build configurations.