Next TeamCity major release wishlist

Dedicated agent feature is already supported by TeamCity. You can navigate to agent/Compatible configuration tab and change run configuration policy to "run selected configurations only". Then select approved configurations with checkboxes.

Yes, but you have to explicitely select the configuration. what I would like would be to define a variable (at the agent level) that the configuration build (in the agent requirements) should met. It is easier that way as I can use a template for all configuration of that kind...

• 21 : Dependancy manager : Artifacts in TeamCity is a nice feature, however we don't use in my company (not for dependancy that is). If TC where providing a new module for dependancy manager (a way to handle dependancy for projects with maybe a dependancy repository based on artifacts (auto provided with simple configuration - an include in build runners...). what I would want is this : in a sln runner, TC parche the sln and try match the dependancy with on in his repository and auto-provide them for tje build. there should be an option for each runner to configure the depancy management (optional) : manual or auto (if possible). In manual, a user could provide a custom process to return dependancy name in a target format (from xml files, or whatever)... well that is the idea. Dependancy management has always been a pain to handle. So if TC would provide a central dependancy repository, that would be a killer feature.
• 22 : Parallel / Sequential / Ordered / Conditional Runner : I have the following build configuration, which would look like this. I want to use serveral runner within my build tasks :
  
  • 0-Retrieve dependancies (I don't want to use artifacts, as It take ressources (space). I prefer to retrieve everytime the depencies for each build (delted on start) .
  • 1-Prebuild actions
    
  • 2-Build my project
  • 3-Run Unit test
  • 4-Do post build action
  • 5-Generate doc
  • 6-Custom deploy process

         Within the same build process I would like to run parallel task as It will save time and accelerate my build time, at the same time I need a wait to explicitely say I want some task to be sequential and ordered.
         I would then like to say this :

• 1 Sequential :
  • Retrieve dependancies
  • Prbuild Action
  • Build my project
• 2 Parralell     
  • Run unit test
  • Do post build actions
  • Generate doc with
    
• 3 Sequential : custom deploy process (conditional if unit test didn't fail)
• 24 : Improve diskspace/Memory management and data purge : I have a very restricted environnement with strict ressource allocation (quota on disk space, limited direct access, etc...). And several time while using TC, I suffered trouble to manage ressources. I have two drives C and D  (with teamcity installed on the D). C is quite small but enougth to work without troubles. Sometimes, I noticed that the server, althought installed on the D, still allocates ressources on the D (for example, when configured CVS setting with checkout on server (svn) the data is savec on the c. An enhancement would be to centralized all the deletable data in the same folder (Teamcity\tmp for ex) and let it be cleanable from the dashboard). Another enhancement on the same, would be to provide more precise clean up option. I notived that the system\message was growing quite large in my case and would like to delete it from the disk. I would like to keep all the statistics in the database and all the logs on the disk and to be able to delete it in an fast & easy way. It may already be the case now but I'm jsut telling what I noticed from my usage of the product. Well to sumurize this point, What I would really like is to have an idea of how much data a build is consuming, It could be in the administration panel, with a details (on demand) for each project, each build with the ability to delete fully or partially the data. It is in my case and opinion a must have feature, because from a administrator point of view with limited rights on the server you can't really live with it...

Well that's it for now.

Stay tuned.

Sano,

Sorry for the delay in replying. I was on vacation for several weeks and only now did I manage to get back to the thread.
Some comments...

> 21 : Dependancy manager

It's OK to use TeamCity's bundled artifacts functionality, but extensive requirements will probably end up with a dedicated product like Artifactory.
Integeration with a dedicated artifact repository seems to be the proper way to do extensive dependency management.

There is a TeamCity plugin for Adrtifactory integration and we plan to develop external repository managers integration. This can be split into specific features and filed into the tacker if they are not yet there.

As discovering dependencies from SLN... Here is a related issue and we think about the approach (however we will probably start with Maven first). At the same time there are many factors to investigate and make a decision on. If you can elaborate on how this should look like in detail, please do (probably in a separate thread).

> 22 : Parallel / Sequential / Ordered / Conditional Runner

Sequential is what we call multiple build runners and it is already baking. Ready to try it in the next TeamCity 6.0 EAP?
As to conditional and parallel: we are not yet sure we should turn TeamCity runners configuration into mini GUI build tool, so for now the recommended way to handle parallel execution is to create several build configurations in TeamCity and run them on different build agents.

> 24 : Improve diskspace/Memory management and data purge

> Sometimes, I noticed that the server, althought installed on the D, still allocates ressources on the D (for example, when configured CVS setting with checkout on server (svn) the data is savec on the c.

Should be filed into tracker if still actual.

> An enhancement would be to centralized all the deletable data in the same folder (Teamcity\tmp for ex) and let it be cleanable from the dashboard).

This already should be done that way. But no clean from dashboard, should be cleaned automatically, I believe. Pelase report all relevant issues so that we can address them one by one.

> I notived that the system\message was growing quite large in my case and would like to delete it from the disk.

A feature request to allo cleaning up  build logs:TW-11710.

> I would like to keep all the statistics in the database and all the logs on the disk and to be able to delete it in an fast & easy way. It may already be the case now but I'm jsut telling what I noticed from my usage of the product.

Any missing feature is to be voted for or filed into the tracker. We do plan to enhance cleanup rules, but just need more detailed feedback on the most necessary features to adjust priorities.

> Well to sumurize this point, What I would really like is to have an idea of how much data a build is consuming

Seems like TW-8725.


As usual, thank you for the thoughtful feedback!

I would love it if when I was installing TeamCity as a Windows service, I could configure it to run on a particular IP address and port as well as install a certificate so that SSL would work out of the box, and I wouldn't have to learn Tomcat and Java to setup secure access to the build server.

Lance,

Thanx. For the HTTPS please vote for TW-12976.
You can also file a request for the bind address part, if you like.