Sad to see that this is still not part of TFS2012.
Rob described how to do this manually here
http://scrumdod.blogspot.ch/2011/04/fail-build-if-code-coverage-is-low.html
Why not?
Look at these numbers:
and this system is deployed twice a day.
Scary if you compare this to our “little” projects
FaceBook ships twice a day
https://www.facebook.com/notes/facebook-engineering/ship-early-and-ship-twice-as-often/10150985860363920
There are 2 options to configure your build output and Vishal highlights the differences between those 2:
Yes this is for Microsoft tooling.
My 2cents
“Transformation” is only applied via VisualStudio and runs during the build.
“Parametrization” is for deployments and runs during deployment.
Now you should ask: How do I configure my app running in production?
There is no answer from Microsoft, so you free to come up with your own solution!
————————
Full article
Web Deployment: Web.Config Transformation
http://vishaljoshi.blogspot.ch/2010/06/parameterization-vs-webconfig.html
Great idea to split database deployments in 2 steps.
The expansion scripts are run at some point prior to upgrading the application and the contraction scripts are run once the system has been upgraded and considered stable. This produces a nice benefit of decoupling database migrations from application deployments. The expansion scripts could be run a day or more in advance of the application deployment at a time that is convenient for database changes. The contraction scripts could be run potentially days after the deployment once everything has been validated with the new release.
Weekly Release Blog #11 – Zero-Downtime Database Deployment
http://exortech.com/blog/2009/02/01/weekly-release-blog-11-zero-downtime-database-deployment/
MS catching up with appHarbor!
Dev checks in code, and afterwards your change is visible on your Azure website.
I wonder how that new build template looks like
Brian Harry’s announcement
http://blogs.msdn.com/b/bharry/archive/2012/06/07/announcing-continuous-deployment-to-azure-with-team-foundation-service.aspx
Mike Fourie’s tutorial with screens and detailed steps
http://mikefourie.wordpress.com/2012/06/10/using-continuous-deployment-to-azure-with-team-foundation-service/
Nice explanation of different environments like: Development, Testing, Staging, UAT and Production.
#1
In one of my last projects we had a “stresstest” environment where we ran stress tests every night from 3AM-5AM.
Did i mention the importance of highlighting the different environments somewhere? Maybe a different web site background color or a big label on top: “STRESS TEST ENVIRONMENT: Stay out!”
#2
Make sure to automate the deployment to those environments as much as possible
RSS feed