Switch deployment to Continuous Delivery

[ThomasLamb]

There is a newer and better way to deploy to production which I've just recently gained experience in. In Azure it's "Continuous Integration". It depends on Visual Studio Team Services and uses their build agents and release agents. I'd like to switch Academic and Career Prep application to use the new way hopefully to the point where everything can be automated, even updating the stable branch. At the very least this will hopefully give more clarity as to what build and code is running in production.

[ThomasLamb]

Created build and release steps in Visual Studio Team Services that link to Azure. 🥂

Now just need to test the full deployment life cycle to see if it works.

[ThomasLamb]

Pull Request validation is working good.

Build process for commits to master are working too, along with deployment to staging, approval, and deployment to production.

The release tagging didn't work perfectly first run through, changing release tagging to use format like v1.0.yyyymmdd.rev to see how that behaves. Otherwise there might be something else need to do to tag release when application is deployed to production.

[ThomasLamb]

Would also be nice to improve the "approval e-mail" to include a link to staging environment.

[ThomasLamb]

Okay, the release process isn't working. VSTS thinks it succeeds at deployment, but in fact it is failing! Nothing is being deployed to staging 😞 😕