slides supporting the session. Talking about YAML, pipelines, spfx, devops, ci, cd and many other thigns

1. How to do DevOps with the
SharePoint Framework and why
it matters?
SharePoint Saturday Toronto 2019
By: Vincent Biret

2. PLATINUM
Thank You Sponsors!
SILVERGOLD

3. 3
SharePint
SharePint
The Drake & Firkin
6982 Financial Dr, Mississauga, ON L5N 8J4
SharePoint Saturday
Toronto #SPSToronto

4. Passionate about technologies, development and community
Vincent Biret
@baywet
bit.ly/vince365
Microsoft Office Dev MVP
Azure and Office 365 developer @ 2toLead

5. Devs, Product Owners, Deciders, QA, Project Managers…
For whom this session is?

6. Agenda
Intro to Software lifecycle + DevOps
Intro to Azure DevOps
Azure Pipelines
Unit tests with SPFx
Intro to tech debt management
Conclusion

7. Ready?

8. Software lifecycle
Where it all begins

9. From the delivery team’s perspective, DevOps is about automating the process, releasing
frequently, and leveraging telemetry as well as feedback to improve solutions
DEVOPS BASICS
Idea/Need
Market

10. Azure DevOps
Let’s talk about tooling

11. Formerly Visual Studio Team Services
Azure DevOps
TFS as a service/modular
Updated more frequently
Pay per user/build
Everything except
SharePoint Integration
Process Template Customization**
Data Warehouse

12. Branch
management
Code as a team, not a guy in a cave

13. Git is great with branches and cross platform, it has become an industry standard
Gitflow is a great process for DevOps teams and allows them to scale seemlessly
Git + git flow
Git is a decentralized source control technology
Branches are cheap
Merging is not a nightmare
Cross platform
Lot of tools
Git flow is a process model for branch management
Focused work
Easy context switching
Standard and no thinking required
Semver…

14. Pull requests are a great way to help your team grow and to improve the quality of the
code
Peer reviews and quality
« Here are a bunch of changes in the code, please review it and make it
part of the main code »
Also check if changes:
Build
Pass unit tests
Pass static analysis gate (code quality)
Have associated work items (context/documentation)
And allows:
For discussion
The team to grow together

15. Build
Let’s increase the quality of releases

16. Implementing automated builds solves multiple concerns for a development team
Automated builds
Predictable result
Constant quality
Time saving

17. Avoid XAML builds (very old) and 2015/JSON builds (previous model)
Pipelines
YAML definition
Web edition
Lot of third-party integrations
Tasks on GitHub!
Agent auto updates!

18. Hosted agents are VM’s ready to use in the cloud with lots of pre-installed tools.
Agents
Hosted Agents
BaaS
Installed Agents
Azure, or anywhere else

19. Azure DevOps includes a wide eco-system or agents and tools by default
Hosted agents flavours
Windows
2019, 2016, 2012R2, core1803
Ubuntu
18.04, 16.04
MacOS
Mojave, High Sierra
Bring your own container

20. Build pipelines
Demo

21. Tests

22. The first thing to consider is how quick you want feedback vs how complex the test is.
Tests levels
Unit testing
Load testing
Integration testing
System testing
Functional/Acceptance testing

23. The second thing to consider is the aspect of the solution you want to test for.
Tests types
Installation
Compatibility
Regression
Destructive
Security
L17N/I13N
A/B
…..

24. Microsoft removed it’s original choices for unit testing from SPFx.
Test tooling – 2019 updated
Runners Assertion
libraries
Emulators -
Environments
Reporters Frameworks Stubing -
Mocking
Snaphosts
Karma Chai + as
promised
PhantomJS Junit Mocha Sinon Jest + Enzyme
MSTest MS.Test ns Node
(backend)
Coverage Casper Jest
Istanbul Jest Chrome Cobertura Jasmine
Jest Enzyme … Jest

25. Unit tests of demo webpart
Demo

26. Deploy
Automate all the things!

27. Both strategies are valid and you should choose the one that fits your team.
Different schools
Source promotion
Track and deploy a certain state of source code
Rebuild for each deployment
Build promotion
Source code is built once
Binaries are deployed to environments

28. The release pipelines allow you to capitalize on the skills developed for build pipelines
Pipelines (release)
Same technology as the build
+ Environments
+ Deployment strategies
+ Approvals

29. Release Pipelines
Demo

30. Technical debt
management
Or how to avoid digging your own grave

31. What is tech debt?
Code we’re not comfortable with
Preventing us from innovating
Causing a lot of support
Stressful for the team

32. Solutions?
Rewrite everything every 2 years
Pair coding
Static analysis + linting

33. SonarQube, linting for demo webpart
Demo

34. Conclusion

35. DevOps methodologies improve the overall productivity and reduce stress of the team.
Conclusion
Lot of time saved
Consistent builds
Automated tests
Quality increased
Money saved

36. Bit.ly/vince365 @baywet slideshare.net/VincentBIRET
Thanks!/Questions?
Vincent Biret
Office 365 and Azure
Developer, 2toLead
@baywet
Bit.ly/vince365
http://bit.ly/az-sq
http://bit.ly/spfx-devops