Slide deck of my session at the collab365 about setting up your release pipeline for SharePoint in Azure. How can Microsoft ALM and cloud services improve the quality of your deliveries
08448380779 Call Girls In Diplomatic Enclave Women Seeking Men
#Collab365 Setting up your release pipeline for SharePoint in Azure
1. Online Conference
June 17th and 18th 2015
WWW.COLLAB365.EVENTS
Setting up release pipeline for
SharePoint in Azure
2. WWW.COLLAB365.EVENTS
Vincent BIRET
Email : vbiret@outlook.com
Twitter : @baywet
Blog : bit.ly/vincentbiret
LinkedIn :ca.linkedin.com/in/vbiret
SharePoint MVP
Products Team Tech Lead
Montreal
5. WWW.COLLAB365.EVENTS
• General Introduction to Software lifecycle
• General introduction to VSO/Azure
• The build system
• High-level intro to deploy and tests for SP
• Conclusion
Today’s Agenda
10. WWW.COLLAB365.EVENTS
• TFS as a service
• Updated more
frequently
• Pay per user/build
• Everything except
– Release Manager
– SharePoint Integration
– Process Template
Cutomization
– Data Warehouse
Visual Studio Online
13. WWW.COLLAB365.EVENTS
• XAML workflows
• Hard to debug
• Only editable with VS
• Requires Controller + Agent
• Updates not automated
• Third party tools hard to integrate
Build
Why should you care? ALM = time saved, happy devs, money saved and better products/services
Might be a little bit different when doing consulting but same idea
Unlimited storage, team projects, everything, 5 free users, free for users with msdn subscriptions, free for stakeholders
Data Warehouse can be replaced by powerbi
http://blog-eng.dbtek.it/2014/03/visual-studio-online-vso-vs-team.html
New, hasn’t yet the build quality information and integration with RM + tests manager. Only on vsonline right now
https://github.com/Microsoft/vso-agent-tasks
Build as a Service (billed by minutes building), Hosted agents have foundation edition of sharepoint installed. Installed agents only need internet access.
Show build section, build agents ( + install), build settings for projects
RM not available online right now, and only works with XAML builds.
Lab studio only works with XAML builds, hard to set up. (whole SC stack to set up)
powershell + Tasks = quick win
Tip: use –verbose everywhere!
App file deployment is complicated but can be achieved via CSOM +PS
App secret+id can be managed via settings + ps.
Other components use traditional vs tools deployment, easy to CI
https://social.msdn.microsoft.com/Forums/sharepoint/en-US/1f0cd45a-00e1-4452-bafe-83c6ee3a59db/can-i-deploy-a-sharepointapp-to-office-365-using-powershell?forum=appsforsharepoint
On prem farms hard to maintain, especially when deploying lot of “buggy” components.
On the fly farms take a lot of time to be up, and a lot of ps to finalize configuration
Office 365 is ready to go, but only for apps
My personal opinion => only bits, no farm as GAC impacts outcome of vs build. + having farm on build machine makes it way more complicated to manage
https://en.wikipedia.org/wiki/Software_testing
Goal of this section is not to cover everything, but more what we can achieve in the SharePoint world
You don’t want to spend your time/money testing SharePoint’s API
Unit testing => complicated to set up, must be well designed
Load testing => sharepoint makes irrevelant
Functional testing => great added value, but costly
Any case it will highly depend on your app/solution’s architecture. The key work is abstract, absctract and abstract!
Money save = dev time saved, less support to provide, better product/service