New WIT for Build Management
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.
We want to build a product that our users love. User Voice provides us a great platform to let any TFS/VSTS user tell us what is important to them. We closely pay attention to the most popular suggestions.
Too many suggestions in User Voice however will make it hard for you to find the suggestions you want to support. We will regularly archive the suggestions created more than a year ago and has low number of supporters.
When a suggestion is archived, you can still view them, but you can’t support them anymore. Also Microsoft will not pay attention to these suggestions.
1 commentComments are closed
André Dias commented
The suggestion above is a way I deployed the following idea https://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/2312746-better-support-to-continuous-deployment-practices for a customer.