Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Continuous Delivery with VS2015 and TFS2015

1,064 views

Published on

Continuous Integration - Continuous Delivery (CI-CD) with Visual Studio 2015 and Team Foundation Server 2015
1) CI/CD Introduction: CI/CD Advantages; CI/CD Practices
2) CI/CD with VS2015&TFS2015
3) Continuos Inspection with SonarQube

Published in: Software
  • Be the first to comment

Continuous Delivery with VS2015 and TFS2015

  1. 1. Continuous Delivery with VS2015 & TFS2015 NguyễnThanhTùng
  2. 2. About me • NguyenThanhTung • Technology Manager at MISA JSC • Microsoft Certified Professional Developer • Technologies: • ASP.NET MVC/Web API • Windows UAP • Windows Forms • WCF/WPF/XAML/Silverlight • AngularJS/ExtJS/Ext.NET • Community: • Blog at: http://tungnt.net • Facebook Page: https://www.facebook.com/tungnt185 • Facebook Group: https://www.facebook.com/groups/hanoinetgroup/
  3. 3. Table of Contents • CI/CD Introduction • CI/CD Advantages • CI/CD Practices • CI/CD withVS2015&TFS2015 • Continuos Inspection with SonarQube • QA
  4. 4. CI/CD Introduction
  5. 5. What is CI? • CI is a software development practice: • Members of a team integrate their work frequently • Usually each person integrates at least daily • Leading to multiple integrations per day • Each integration is verified by • An automated build (including test) to detect integration errors as quickly as possible. • Source:http://martinfowler.com/articles/continuousI ntegration.html
  6. 6. CI/CD Advantages • For development the benefit of CI/CD are: • Removed of manual copy/paste deployment • Prevention and reduction of production & staging errors • Generation of analysis & reporting on the health of the code base • For operation the benefit of CI/CD are: • Reducing risk • Reducing cost across the development & deployment process • Enhancing the reputation of the company by providing Quality Assurance
  7. 7. CI/CD Advantages
  8. 8. CI Process
  9. 9. Continuous Integration 1 - Maintain a Single Source Repository 4 - Everyone CommitsTo the Mainline Every Day 5 - Every Commit Should Build the Mainline on an Integration Machine 2 - Automate the Build 3 - MakeYour Build Self-Testing 6 - Fix Broken Builds Immediately 7 - Keep the Build Fast 8 - Test in a Clone of the Production Environment 9 - Make it Easy for Anyone to Get the Latest Executable 10 - Everyone can see what’s happening (Source: http://www.martinfowler.com/articles/continuousIntegration.html) CI/CD Practices
  10. 10. CI/CD to DevOps • DevOps practices: • Communication • Collaboration • Automation • Monitoring
  11. 11. CI/CD with VS2015 & TFS2015
  12. 12. TFS + Visual Studio Online
  13. 13. TFS Build Architecture • Build Agent: • Perform actual work • Can installed on any machine supportTFS • Installed as Windows Service • Build Pool • Contains agents • Defined on server • Have own security permissions • Build Queue • Defined at project collection level • Group build definitions to specific pool
  14. 14. CI/CD with TFS2015 Configure Build Agent Create Build Definition Configure CI/CD
  15. 15. Build Agent • VSO support one build at a time • < 30 minutes run • < 10 GB storage • 240 minutes/month
  16. 16. Build Definition
  17. 17. Configure CI/CD
  18. 18. CI/CD run with real-time status
  19. 19. Qualities management with SonarQube
  20. 20. Using FxCop Code Analysis /p:RunCodeAnalysis=True /p:CodeAnalysisRuleSet=AllRules.ru leset
  21. 21. SonarQube • Sonarqube is an open source quality management platform, dedicated to continuous analyze and measure source code quality => continuous inspection • http://www.sonarqube.org/
  22. 22. SonarQube
  23. 23. Thanks for your listening! Q&A?

×