With a few simple tweaks to the build and release definitions (as long as you follow a naming convention) things can be easily changed to use more of the built-in variables so that the definitions be easily cloned from one integration to another without any changes. Much like I tried to simplify some things and keep my talk focused I will with this post.Īs far as the actual build, release and deploy process much can be improved and made even easier than it is. There are many more steps and actions we have taken along those same lines, and perhaps I will have more blogposts about it, however I will try not to make a mess of the red thread of this post by getting side tracked with those.
MICROSOFT VC80 ATL CODE
One of the goals is also to limit the amount of work each developer has to do when building an individual integration and offloading some of that to the build and release steps, like for example creating a resource group template for deploying the developed Azure Function or adding the code to enable diagnostics in every Logic Apps resource group template. The primary purpose of creating this process is the requirement to have a repeatable build, release and deployment pipeline that would look the same, work the same, and be configured the same way for all developers in the team over time building a lot (think in terms of 1500+) integrations based on Logic Apps.
As well as stepping through the actual Visual Studio Team Services configuration step by step with screenshots and configuration strings. What I’d also like to share is the sample code and scripts that I used, available here. The video and slides are available on the INTEGRATE2017 site (or will be soon) and the slides are also available from me here. In it I showcased a process for doing just what the title says: A process for developing Microsoft Azure Logic Apps solutions with GIT source control hosted in VSTS and using the build and release management capabilities to package and deploy Logic Apps, Integration Account artifacts schemas and maps, as well as Functions.
I had a session: “Logic Apps continuous integration and deployment using Visual Studio Team Services”. Regardless if you were there this year or not I very much encourage you to be there next year (or catch the US version in October). Fantastic event! If you’ve never been, in short it’s an integration focused event running over the period of a couple of days in London featuring Microsoft product group and community speakers. So, INTEGRATE2017 just ended (actually at the point this post is out it ended about a month ago). or “The code to my INTEGRATE2017 session”.