I have read various threads on this forum to do with bespoke automated deployment of built code to servers. they all present interesting ways to achieve an automated deploy from TeamCity with whatever pros and cons go with that method. But I was wondering if any plans were in the cooking pot for TeamCity to extend into the continuous deployment' space. It seemed that, with the introduction of build steps, that continuous deployment was an idea in someone's head in your offices but despite watching the blog like a hawk I am yet to catch a hint of it coming true.
In my opinion, TeamCity is well placed to offer this functionality (although I'm not saying it would be easy to implement), by that I am referring to, for example, a special build step that requires manual invocation or authorisation before it commences. Maybe in later versions the ability to be executed against a number of different environments as defined in somewhere else TeamCity's config would be added. With this addition TeamCity really has just about everything needed to then call itself an 'Application Life-cycle Management' tool (for those who care about such buzz). As TeamCity already offers static analysis, code coverage, etc.
what does everyone else think?