slides of my session at the SharePoint saturday Calgary 2016 about how to set up a release pipeline for SharePoint/Office 365 development in Azure with Visual Studio Team Services
8. 8 | SharePoint Saturday Calgary – 23 APR 2016
Software lifecycle : devops
Plan
Dev
Test
Production
Idea/Need
Business
Plan
Marketing Sales
Market
Feedback
Agile/CMMI/
…
Architecture
Source
Control
IDE
Build
xTests
42. SAVE 40% on print books with code
MSUSERGROUP
SAVE 50% on eBooks with code
MSUGEBOOK
*Codes can not be combined with another offer or eBook Deal of the Week feature titles.
Visit microsoftpressstore.com today!
Devs, devops, qa people, deciders
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
https://www.visualstudio.com/get-started/overview-of-get-started-tasks-vs
Unlimited storage, team projects, everything, 5 free users, free for users with msdn subscriptions, free for stakeholders
Data Warehouse can be replaced by powerbi or dashboard being delivered
RM currently in preview (since 5 days ago)
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 (oceanik grunt)
RM now available in preview!!! Game changer!!!
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
http://blogs.msdn.com/b/vesku/archive/2015/11/20/automating-add-in-app-installation-to-sharepoint-sites-using-csom.aspx
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
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, abstract and abstract!
If the static analysis could be automated, wouldn’t be it great?
Money save = dev time saved, less support to provide, better product/service