I use a lot of different computers and I have a thing for reimaging my computers way too often. All in all, this means that I find myself sitting in front of a newly installed computer quite often. One thing that I always to on a fresh computer is to clone a bunch of repos from my personal organization in Azure DevOps that contains my notes and a selection of tools that I want available everywhere I go.
Continuously building and deploying new versions of my modules to internal repositories (or PowerShell Gallery) is something I really like. That way I can just push my code and let the automation handle the rest. Here are some learnings I’ve made. Deploy on tag Firstly, I usually only trigger a deploy-workflow on tags, this way I can manually decide when to do a release and what version it will have without relying on any complex methods.
In a previous post I wrote about when Iupdated the command Update-AzureRMto only update modules that has a newer version available and not download and overwrite modules that already are up to date. Unless I use the -Force parameter of course. Once I've done the change and was satisfied I thought that maybe someone else might benefit from this update and since the AzureRM module is available as an open source project on GitHub I requested to have my changes included in the official version of the module.
<p> I'm an Ops guy, I have a history of working in IT operations and I think of myself as a “technician” or “ITPro”. To be honest, I don't know what to call it, but my point is that I do not have a background as programmer. I've been talking with other Ops-persons about integrating and collaborating with developer teams for quite some time now.