Visual Studio Release Management - New weltanschauung or natural evolution? @ Swansea SDC
Download as PPTX, PDF2 likes388 views
Visual Studio Release Management is a DevOps tool for deploying software easily and frequently. It allows managing the release of packages built by development teams to QA and production environments. Release Management helps coordinate the teams responsible for operating and monitoring environments. It provides an approval flow and aims to implement continuous delivery by automating deployments. While initially only available on VSTS, an on-premise version will be released with Visual Studio 2015 Update 2 which adds additional features like skipping deployments and multiple approvers. Release Management brings build and deploy processes together but has some limitations initially with its task library and lack of inheritance between release definitions.
Visual Studio Release Management - New weltanschauung or natural evolution? @ Swansea SDC
- 1. Visual Studio Release Management: new Weltanschauung or natural evolution? Giulio Vian http://blog.casavian.eu/ [email protected] @giulio_vian http://www.getlatestversion.it/
- 2. Who am I? • 25 years experience • 14 years • Currently • Me? I’m just an OpsDev, you can tell it by the way I walk… • Some works on GitHub • TfsAggregator2 • TfsGitAdmin • GitPushFilterPlugin • since 2010 • If I do not speak English (or sounds weird to you) stop me
- 3. Will talk about? • Visual Studio Release Management „vNext“ • Available on VSTS • On premise with 2015 Update 2 • Questions to be answered • What is? • Costs • Advantages • Complexity • Idiosyncrasies Said undelicately, in the cloud, we can release features that aren't finished yet. Brian Harry 100/200-level session!
- 4. What is Visual Studio Release Management “vNext”? «DevOps solution for delivering your software easily and more frequently» An automation technology very similar to Build v.Next designed to support deployment New implementation WRT InRelease, 2013 o 2015 Tool to properly implement Continuous Delivery
- 5. What is Visual Studio Release Management “vNext”? «DevOps solution for delivering your software easily and more frequently» An automation technology very similar to Build v.Next designed to support deployment New implementation WRT InRelease, 2013 o 2015 Tool to properly implement Continuous Delivery
- 6. My own definition • A tool to manage release of packages, built by internal or external development teams, to QA and production environments, be they in house or external, helping coordinate with teams responsible for operation and monitoring QA and production environments • Shortly, what happens after the build
- 7. Martin Fowler says… • You’re doing continuous delivery when: • Your software is deployable throughout its lifecycle • Your team prioritizes keeping the software deployable over working on new features • Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them • You can perform push-button deployments of any version of the software to any environment on demand Source: http://martinfowler.com/bliki/ContinuousDelivery.html
- 8. Demo Development using VSTS (cloud) and release on-premise
- 9. Availability and costs • Currently VSTS-only, but Update 2 is just around the corner • First hosted agent is ‘free’ • Hosted Agent (i.e. runs on an Azure VM) • €33,73 / month • £24.44 / month • Private Agent (on premise) • €12,65 / month • £9.16 / month
- 10. Advantages • Build ≠ Deploy • Approval flow • Say bye to XAML
- 11. Complexity • Limited task library • A good thing? • Variables flow • Manage server farm • Global Objects • Service Endpoints
- 12. Idiosyncrasies (PITA in en-US) • Migrating from earlier versions • http://blogs.msdn.com/b/visualstudioalmrangers/archive/2015/12/09/releas e-management-workflow-migrator.aspx • No inheritance or sharing • Would be nice to share Credentials between Release Definitions • Tasks are mostly designed for a single machine • But using Azure… • …or some Powershell trick… • …or Azure Stack some day
- 13. Chicken or egg? (bootstrapping) 1. Install the agent • Do not need being an admin • Credentials specified in Release Definition • TFS / VSTS on sight view (HTTP/S) • Use a pre-canned VM image, DSC, Chef, … to install 2. Configure the machine • Pre-requisites, e.g. IIS, WebDeploy 3. Install your Application
- 14. Caveats • Approvers like cops • Agent Pools to insulate environment (e.g. production from dev) • An environment is not an environment • Security • Agent Pool Admin Account VSTS / TFS Instance • Agent Queue Administrators / Users Collection • Release Administrators Project • Creating new Release is powerful • Limit accesses
- 15. Update 2 • No more sequential Environment • Skipping intermediate un-deployed Releases • Set Release time schedule while approving • Multiple approvers (and/or) • Auto “Release notes” • TFS on premise • Source: http://blogs.msdn.com/b/visualstudioalm/archive/2016/01/08/vsts-release- management-plan-for-2016-h1.aspx
- 16. New Weltanschauung o natural evolution?
- 17. To know more • Official Documentation • https://msdn.microsoft.com/en- us/Library/vs/alm/Release/overview • HOL at • https://github.com/Microsoft/PartsUnlimited/blob/hands-on- labs/docs/HOL_PartsUnlimited_WebSite_Continuous_Deployment /HOL_Continuous_Deployment_Release_Management.md • Continuous Delivery with Visual Studio ALM 2015 — M.Olausson, J.Ehn (Apress) • http://www.amazon.it/Continuous-Delivery-Visual-Studio- 2015/dp/1484212738/
- 18. Free Resources for DevOps Practices • Optimize your DevOps practices and tools: • Get started on your DevOps journey: aka.ms/devops • Download the Forrester Infrastructure-as-Code whitepaper: • Complexity kills. Automate with Infra as code: aka.ms/iac_tlp • Technical resources for Practitioners: • Get access to free online training: aka.ms/devopsmva • DevOps Maturity Self-Assessment • See where your organization is at across 7 areas: http://devopsassessment.azurewebsites.net/ • Learn DevOps Practices hands-on with PartsUnlimited apps • github.com/Microsoft/PartsUnlimited and github.com/Microsoft/PartsUnlimitedMRP Accelerate your application delivery lifecycle
- 19. Call to action
Editor's Notes
- #3: https://github.com/giuliov/TfsGitAdmin https://github.com/giuliov/GitPushFilterPlugin https://github.com/tfsaggregator/tfsaggregator http://www.radiotfs.com/Show/105/TFSAggregator2withJesseHouwing
- #9: N.B. using VSTS, cloud ≠ public! https://giuliovdev.visualstudio.com/DefaultCollection/_git/RMDemo2016H1
- #10: bagigi
- #12: Service Endpoints are defined at Collection level
- #17: It is both: a totally new implementation BUT based on InRelease data model and Build.vNext While there are many things that should be refined, I see solid ground Hope to see some process-oriented tasks, e.g. gradual roll-out on a farm
- #20: Not covered today: Non-Windows agents and platforms Deploy on Azure Deploy on other cloud environment, e.g. AWS