If you've read my previous posts on the topic, you might have already guessed that I am a big fan of maintaining builds as code artefacts. I was super excited when the Visual Studio Team Services (VSTS) team announced YAML support and I knew right then that this had to be part of generator-nullfactory-xrm.
With version 1.6.0, I've added the ability to generate tailored YAML build definitions into your Dynamics 365 projects. What this means is that you get rich CI build support right out of the gate! No more excuses for not having a CI build in your project!
The option to generate a CI build is defined as a sub-generator. This is intentional as I didn't want to automatically assume that everyone would be using VSTS as their source control.
Here's the quick rundown of the steps necessary to get things up and running. What we're aiming for is a layered approach:
First generate the default project structure.
Next, generate the YML file using a sub-generator.
Push changes to remote VSTS git repository.
Verify that VSTS provisioned the YML file as the CI build.