The Release Pipeline To create a release pipeline, you need to specify one or more artifacts you want to use (the output of the previous "build pipeline"), then you setup your "stages" where each stage has again a set of tasks. There are more parts available:Azure DevOps CI/CD for Windows Desktop Apps - Part 1Azure … Continue reading Azure DevOps CI/CD for Windows Desktop Apps – Part 4
Kicking off the Release Pipeline When you configure a release pipeline (which we discuss in Part 4), we need to have a "trigger" which lets us know when we actually want to start the release pipeline. There are many ways to handle this. In my particular scenario we are going to use the #PUBLISH tag … Continue reading Azure DevOps CI/CD for Windows Desktop Apps – Part 3
Controlling the Build Pipeline As stated in the "My Goal" section of my previous post, I want to start a build only when a commit message has some predefined tag or identifier. This is useful if you want to make sure that only the solution/projects you are interested in are built in a larger "mono-repo". … Continue reading Azure DevOps CI/CD for Windows Desktop Apps – Part 2
The most important thing for any app is a consistent build/deployment process. I've been doing DevOps and CI/CD for many years now and having manual build/release steps is a huge source for errors and issues. Every single time I kick off a build and release, I'm happy and smiling because everything is running smooth and you don't have to worry about messing things up. But getting their is a real challenge!
Every year or two, I find myself re-evaluating virtualization options for macOS. For the past two years or so, I was using Parallels and as a developer who is mostly using Visual Studio, it worked quite well. To clarify, I use my VMs almost exclusively for software development. All the other tasks, like emails, browsing … Continue reading VMware Fusion vs Parallels