As I Build Master, I would like to deploy a pre-existing Build to several environments considering different configurations to assure that the same binaries tested in the staging environment is promoted to production environment.

Today, we can do it using custom events in Build Quality and developing a lot a code. However, this solution does not offer a good workflow mechanism, has security issues and requires a lot of administrative effort.

My proposal is having a new WIT that would be created optionally by a build definition. This new WIT would have some states such as New, Development, Staging and Production and, after each state changes, a “partially build definition” would be triggered in order to run specific scripts to promote the binaries and run custom actions between environments.