1 of 9: Working on my "#DevOps on an #IoT World" talk for @DevopsNotts... I've got a full @AzureDevOps CICD pipeline working for #IoTEdge using two @Raspberry_Pi s. @MicrosoftIoT @azure @msdevUK 
2 of 9: The IoT Edge Module code is checked into a @AzureDevOps Git Repo.
3 of 9: The Build Pipeline is triggered off the check in.
4 of 9: A second @Raspberry_Pi is used as a Self Hosted Build Agent as Azure doesn't have a compile option for Arm32 sadly...
5 of 9: The built artifacts are then delivered to the pipeline triggering the Release Pipeline to kick off. First the Deployment Manifest is created, which transforms the existing deployment.template.json file. Variable Substitution adds the Registry Details and module Build No
6 of 9: Next, the Release Pipeline pushes the built IoT Edge Module to the Registry, ready for the main @Raspberry_Pi Edge Device to download and use.
7 of 9 (from @StarTrek.. Teehee): The IoT Edge Runtime on the main @Raspberry_Pi will see the change in Module Version (which is the CI Build Number), and download the latest version of the Module Automatically.
8 of 9: This took a bit of work to hang together, as only parts of Raspbian Stretch, Buster & Python are supported for the various Self Hosted bits on the Pi. Which meant re-imaging my IoT Edge Build Pi SD card a heap of times until I figured out a sequence of steps that worked.
9 of 9: I also had a mismatch between my Build Manifest and Publish steps which meant the wrong DeploymentTemplate file was being used, meaning the final step would fail each time. (Thanks @lrgulliver!)
@lrgulliver Interestingly, it seems to take about 10 minutes for updated modules to make their way down to the Edge Device... I'm guessing it's doing a slow poll here? I set the ball rolling about 3 minutes after the last update - So about 10 minutes in total.
