sharepoint saturday houston setting up your release pipeline with azure
TRANSCRIPT
1
Setting up your release pipeline for SharePoint/Office 365 in Azure
Vincent Biret
2
Welcome to SharePoint Saturday Houston
• Please turn off all electronic devices or set them to vibrate.• If you must take a phone call, please do so in the hall so as not
to disturb others.• Special thanks to our Diamond Sponsor, HSPUG
Thank you for being a part of the 7th Annual SharePoint Saturday
for the greater Houston area!
3
Thanks to all our Sponsors!
4
Information• Speaker presentation slides should be available
from the SPSHOU website within a week or so
• The Houston SharePoint User Group will be having it’s next meeting Wednesday April 20th. Please join us at www.h-spug.org
5
Click to edit Master title styleVincent BIRETOffice Servers And Services [email protected]/vince365
Products Team Tech Lead
Montreal
6
Who’s that session for?
7
Session’s objectives
• High-level understanding of ALM• Being able to set up builds for SP
projects• Being able to set up RM for Apps• High-level understanding of
testing/QA• Technical Debt Management
8
Today’s Agenda
• Intro to Software lifecycle• Intro to VSTS/Azure• The build system• High-level intro to deploy and tests
for SP• Intro to tech debt management• Conclusion
9
Click to edit Master title style
WHERE IT ALL BEGINS
Software Lifecycle
10
Software lifecycle : devops
Plan
Dev
Test
Production
Idea/Need Business Plan
Marketing Sales
Market
FeedbackAgile/CMMI/…Architecture
Source ControlIDEBuild
xTests
11
Click to edit Master title style
LET’S TALK ABOUT TOOLING
Visual Studio Team Services and Azure
12
•Microsoft’s Cloud platform• IaaS, PaaS, SaaS• Literaly tons of services• You’ve probably heard about it
13
Visual Studio Team Services
• TFS as a service• Updated more frequently• Pay per user/build
• Everything except– SharePoint Integration– Process Template
Customization**– Data Warehouse
14
Click to edit Master title style
LET’S INCREASE THE QUALITY OF RELEASES
Build
15
Automated builds
• Predictable result• Constant quality• Time saving
16
Build
• Hard to debug• Only editable with VS• Requires Controller + Agent• Updates not automated• Third party tools hard to integrate
17
Build 2015
• JSON definition• Web edition• Lot of third parties integrations• Tasks on github! (see notes)• Agent auto updates!
18
Agents• Hosted Agents– BaaS
• Installed Agents– Azure, or anywhere else
19
Click to edit Master title style
BUILD SECTION, BUILD AGENTS 2015
Demo
20
Click to edit Master title style
AUTOMATE ALL THE THINGS!
Deploy
21
Options available
**
22
FTC Deployment
• Easy to automate
• PowerShell is your friend
23
Apps Deployment• SharePoint Hosted
• Provider Hosted
24
Targets
25
Should SPFarm be created on build machine?
Pros• Deployment easier• Unit testing easier
Cons• Heavier footprint• Can impact build
26
Click to edit Master title style
LAPRESS AND OCEANIK DEPLOYMENT WITH RM
Demo
27
Click to edit Master title style
FINAL TOUCH TO QA
Test
28
Tests levels
• Unit testing• Load testing• Integration testing• System testing• Functional/Acceptance testing
29
Tests types
• Installation• Compatibility• Regression• Destructive• Security
• L17N/I13N• A/B• …..
30
Testing tools
• Mstest• Nunit• xUnit• Grunt• Gulp• …
31
Testing in the SharePoint World
• Provisioning model– Complex– Closed
• OM hard to emulate/test against
32
Tests with FTC
• Almost impossible• Comes at great investments
33
Tests with Apps
• Easy for everything out of SharePoint
• Harder for SP-Hosted Apps
34
Click to edit Master title style
UNIT TESTS OF LAPRESSE
Demo
35
Click to edit Master title style
TEST PLAN OF OCEANIK
Demo
36
Click to edit Master title style
OR HOW TO AVOID DIGGING YOUR OWN GRAVE
Technical Debt Management
37
What is tech debt?
• Code we’re not comfortable with• Preventing us from innovating• Causing a lot of support• Stressful for the team
38
Solutions?
• Rewrite everything every 2 years• Pair coding• Static analysis
39
Click to edit Master title style
SONARQUBE FOR OCEANIK
Demo
40
Click to edit Master title style
TIME TO SAY GOODBYE
Conclusion
41
Conclusion
• Lot of time saved•Consistent builds•Automated tests•Quality increased•Money saved
42
Questions?
Thanks for attending!
