Uploaded byPeter Gfader
Continuous Delivery with TFS msbuild msdeploy
This document discusses automating software deployments using tools like msbuild and msdeploy to enable continuous deployment and delivery. It outlines the pain points of manual deployments and goals of automating deployments. It provides guidance on setting up continuous integration, automated testing, packaging, and configuration for both new systems and existing environments. It also lists best practices like deploying early, having rollback plans, logging builds, and automating as much as possible.
More Related Content
Similar to Continuous Delivery with TFS msbuild msdeploy
Continuous Delivery with TFS msbuild msdeploy
- 1. With msbuild andmsdeployContinuous DeploymentDelivery -----------
- 2. AbstractIf you aredeploying your software manually, you are doing it wrong. If you deploying once a month, you are doing it wrong. If you as a developer are deploying from Visual Studio by clicking "Publish", you are doing it wrong. If a bug-fix takes you 1 hour but your customer needs to wait a week until he gets it, you are doing it wrong. Manual deployments are NOT fun. There is a nice way on how to automate the deployment with TFS 2010, msbuild and msdeploy.
- 4.
- 5. Continous DeploymentDeploy continously...Aftereach change...To a certain env...Continous DeliveryBe production ready...through dev cycle...release any time...
- 6. Peter GfaderAustralia (myfun)Italy (my country)German (my language)blog.gfader.com (my findings)@peitor (my conversations)www.SSW.com.au (my company)
- 7. Deployment AgendaPainGoalsHow ToStartfrom scratchExisting SystemBest Practices
- 8. How do youdeploy?
- 9. How do youdeploy?Web App
- 10.
- 11.
- 12.
- 13.
- 14.
- 15.
- 16.
- 17.
- 18. "Only Bob knowshow to deploy ... And he is on holidays..."
- 19.
- 20. Manual deployments areerror proneDeployment Instructions.docx
- 21. Manual deployments takehours instead of minutes or secondsDeployment Instructions.docx
- 22. Manual deployments takehours instead of minutes or secondsLong feedback cycle We want fail fastDeployment Instructions.docx
- 23. Deployments late inthe development processcause stress on the "deployment day"
- 24.
- 25.
- 26.
- 27.
- 28. Deliver business valuefaster
- 29. Deliver business valuefasterYou spent an hour on a bug fix, but customers will not see it for months
- 30.
- 31. Fail fast andearly in the development process
- 32. Fail fast andearly in the development processOn the "Go Live Day" you realize: Production hardware is missing an important feature
- 33.
- 34. Release small incrementsDeployingoften, less number of defects
- 35.
- 36. This is thehard part, but some rules of thumbHow To
- 37. How ToStart fromScratch Existing Environment
- 38.
- 39. Start from scratch1.Setup Continous Integration
- 40. Start from scratch1.Setup Continous IntegrationCI toolsTFSTeamCityCruiseControl.NET
- 41. Start from scratch1.Setup Continous IntegrationCI toolsBuild automationmsBuildnAntnRakeFinalBuilder
- 42. Start from scratch2.Have automated tests
- 43. Start from scratch2.Have automated testsUnitIntegrationSmokeAcceptanceStresstestBVTWTF?
- 44. 3. Setup packagingsoftware
- 45. 3. Setup packagingsoftware
- 46. 3. Setup packagingsoftware
- 47. 3. Setup packagingsoftwareResult
- 48. Install of package ----------- - ---
- 49.
- 50. 4. ConfigurationXML TransformsvsXML Parametrization
- 51. 1. Web transformsAppliedon every deployment
- 52. Part of VS2010(no UI)
- 53. XML transform engineis wrapped in msBuild1. Web transformsEverything that is not environment specific1. Web transformsEverything that is not environment specific
- 54. E.g.Remove all devsettingsDebug options..
- 55. 2. Web parameterizationAppliedon every deployment
- 56. Run through msDeploy2.Web parameterization2 partsDeclare parametersSet parameters
- 57.
- 58.
- 59.
- 60.
- 61.
- 62.
- 63.
- 64.
- 65. Existing EnvironmentDocument yourmanual deployment processSoftware artefactsConfiguration artefactsTarget environment(s)
- 66.
- 67. Existing Environment2. Improvein baby stepsIdentify your most expensive manual stepAutomate thatRinse and repeat
- 68. Existing EnvironmentEveryone shouldwork together
- 69. Deployment @AuctionsPlus On a napkin
- 74. Automated DeploymentWed night@Sydney .NET UG
- 77.
- 78.
- 79. Deploy earlyDeployment isnever easy, so try to deploy as soon as possible to remove all roadblocks
- 80.
- 81. Have a rollbackplan
- 83. Have a DashboardLatestBuilds?Environment, version?Everything healthy?
- 86. Have a guineapigAB testing
- 87. Have a cloneof your production environment
- 88. Have everything undersource control
- 89. Have everything undersource controlDeployment artefacts.bat.ps
- 90. Log failed andsuccessful builds
- 92. Only let thePO deploy to Production
- 94.
- 96.
- 97. Deployment AgendaPainGoalsHow ToStartfrom scratchExisting SystemBest Practices
- 98. ReferencesDo you automateyour deployment process? (aka Continuous Deployment)http://blog.gfader.com/2010/12/do-you-automate-your-deployment-process.html
- 99. ReferencesAutomating Deployment withMicrosoft Web Deployhttp://weblogs.asp.net/scottgu/archive/2010/09/13/automating-deployment-with-microsoft-web-deploy.aspxTeam Build + Web Deployment + Web Deploy + VS 2010 = Goodness http://vishaljoshi.blogspot.com/2010/11/team-build-web-deployment-web-deploy-vs.html
- 100. ReferencesWeb Deployment MadeAwesome - Scott Hanselman Videohttp://www.hanselman.com/blog/WebDeploymentMadeAwesomeIfYoureUsingXCopyYoureDoingItWrong.aspxTroy Hunt - Blog Serieshttp://www.troyhunt.com/2010/11/you-deploying-it-wrong-teamcity.htmlWeb.Config Transformationhttp://blogs.msdn.com/b/webdevtools/archive/2009/05/04/web-deployment-web-config-transformation.aspxWeb.config Parametershttp://msdn.microsoft.com/en-us/library/ff398068.aspx
- 101. ReferencesReleasing features @Flickrhttp://code.flickr.com/blog/2009/12/02/flipping-out/18questions - Choosing a CI toolhttp://weblogs.asp.net/rosherove/archive/2010/01/21/18-questions-to-ask-yourself-when-choosing-continuous-integration-and-build-automation-tools.aspxJez Humble's work bloghttp://continuousdelivery.com/Web Deploy 2.0http://blogs.iis.net/msdeploy/archive/2011/04/05/announcing-web-deploy-2-0-refresh.aspx
- 102. Thank you!Slides andall detailshttp://blog.gfader.com
Editor's Notes
- #2 Continuous Delivery with TFS, msbuild and msdeployFeel free to copy and use.Drop me a note before though: peter@gfader.com http://blog.gfader.com/
- #4 If you are at the stage where you actually have to think about deployment, that is a Success!There are heaps of projects that didn't get so far .... and I was working on some...
- #6 Continuous Delivery"Keeping systems production-ready throughout development, so that they can be released to users at any time" Continuous Deployment"Deploy continuously to a certain environment"
- #9 From VS: PublishDocx
- #10 From VS: PublishDocx
- #19 Deployment is hard, because of configuration and starting/stopping of external dependencies (web-servers, DBs, queues, external services, …)(web-servers, DBs, queues, external services, …)
- #26 Small feedback cycle
- #27 Small feedback cycle
- #28 Less number of defects
- #29 Less number of defects
- #30 Goal of tests: Is application production-ready?
- #33 I have VS2010 + TFS as build server + a website hosted on DiscountASPhttp://twitter-fish.com/http://twitter-fish.com/Latest/
- #34 Devs check in code to Version control, The automated CI system monitors changes in source control and gets changes. Build and runs all tests. Results are posted back on a portalCI tools are the triggers that listen to various “events’ in the network (a check-in to source control, for example could be a trigger. You can configure these tools to do a few simple things when an event happens. One of those things can be to invoke one of the tools in the previous list. Some of the CI tools, though, include a few simple built in build atomation power (such as built in MSBuild support, or running tests)
- #35 Devs check in code to Version control, The automated CI system monitors changes in source control and gets changes. Build and runs all tests. Results are posted back on a portalCI tools are the triggers that listen to various “events’ in the network (a check-in to source control, for example could be a trigger. You can configure these tools to do a few simple things when an event happens. One of those things can be to invoke one of the tools in the previous list. Some of the CI tools, though, include a few simple built in build atomation power (such as built in MSBuild support, or running tests)
- #36 Devs check in code to Version control, The automated CI system monitors changes in source control and gets changes. Build and runs all tests. Results are posted back on a portalCI tools are the triggers that listen to various “events’ in the network (a check-in to source control, for example could be a trigger. You can configure these tools to do a few simple things when an event happens. One of those things can be to invoke one of the tools in the previous list. Some of the CI tools, though, include a few simple built in build atomation power (such as built in MSBuild support, or running tests)
- #41 In your Build definitionGo to “Process” -> “Advanced” -> “MSBuild arguments” and enter:a. /p:DeployOnBuild=Trueb. /p:DeployTarget=MsDeployPublish/p:Configuration=Release/p:CreatePackageOnPublish=True /p:DeployIisAppPath=[TwitterFish]/p:MsDeployServiceUrl=https://[DiscountAspSERVER]:8172/msdeploy.axd/p:AllowUntrustedCertificate=True
- #43 Or use VS2010http://kb.discountasp.net/KB/a792/how-do-i-deploy-visual-studio-2010-web-application.aspx
- #49 Tell MSDEPLOY this is a config setting
- #50 Tell MSDEPLOY this is a config setting
- #59 Identifysoftware artefactsconfiguration artefactstarget environment(s)
- #62 (Dev's, Ops, DBAs)
- #73 Deployment is never easy, so try to deploy as soon as possible to remove all roadblocksJuval Löwy encourages the build master to deploy after a couple of days after the project start.
- #75 Even with automated tests and UAT there can always slip through a broken release...
- #77 Which version of your software is installed in which environment
- #80 Deploy to a staging environment, once 100% happy deploy to productionNew Zealand is Facebook guinea pig
- #81 Have a clone of your production environment where you deploy and test your software
- #82 Deployment artefacts. Trace changes, have history, evolution of code
- #83 Deployment artefacts. Trace changes, have history, evolution of code
- #86 Authorization
- #90 http://twitter.com/#!/DEVOPS_BORAT/status/65880152705470464
- #96 http://twitter.com/#!/DEVOPS_BORAT/status/65880152705470464