With the above configuration, every check-in from a developer will trigger a build followed by deployment to staging environment. If the team size is huge and involves too many builds per day, we can batch the builds and schedule releases as required. By default, VSTS contains a 30-day' retention policy for the build drops, so any old drop can be deployed to rollback by selecting the build number from the history. The following picture shows the result of release trigger by the continuous integration process once a new build drop is available.
What makes an application great and successful? If having an automated, flexible and error-free build and release pipeline is one part of the answer, having a good telemetry solution which can help diagnose how the application is performing and how it is being used by the customers is another part. Telemetry solutions can capture the usage statistics, errors...
