26SEP2018: I have updated the title of this post to reflect the announcements here and here sharing that canvas PowerApps & Flow are now included in the same solution packaging I describe in this post. I've also changed the title to use "Azure DevOps" instead of VSTS per the name change announced here. This post and video still only go through the process with the Common Data Service, model-driven PowerApps, and Dynamics 365 CE extensions using the old VSTS. While I haven't gotten around to updating the videos, and some of the experiences have changed, hopefully this post can still serve as a guide to help you understand the fundamentals of how to do this with canvas PowerApps & Flow using Azure DevOps. You might have to connect the dots a little, but until I can to more meaningful updates for this blog post and video, I wanted to make sure the "Oh, I can do this now with canvas PowerApps and Flow now too!" lightbulb goes off. HTH
This is the second part of a two part video. The first part is here:
The second video won’t make as much sense if you don’t watch the first video. In this video, I build on the work I did to get a model-driven PowerApp (the artist formerly known as XRM…as I like to say) into source control by showing how to enable deployment automation using Package Deployer, including setting up initial data using the Configuration Migration tool. Then, I show you how to use Visual Studio Team Services (VSTS) to build all the assets in source control into their deployable form. Finally, I show you how to then use VSTS to automate the deployment of those assets to one or many environments. One of the things I highlight in the video is the Dynamics 365 Build Tools on the Visual Studio Team Services Marketplace. These tasks greatly improve the productivity of using VSTS with Dynamics 365 & the Common Data Service.
All of the things I do from scratch in these two videos are the foundation of some of the more advanced things I highlight in the Dynamics 365 model-driven PowerApp DevOps work I mention here: