Jenkins is a powerful, albeit confusing, tool. You can structure all manner of automated processes to build source code, distribute packages, and automate the boring stuff. It's great! But Jenkins and Windows (or... Winders) don't always play nicely. I learned this the hard way in my "day-job" and had to find a technique to resolve some of this bad-behavior. So hopefully you might find this helpful!

I was recently asked "why do you run your own servers, when there's perfectly good, cheap, cloud providers?" Well... Here's why!

Some people keep their creepy Christmas decorations in their basement. Others keep their continuous integration servers down there too...

Run DevOps CI/CD pipelines on industrial equipment with no moving parts? Ok! Sign me up!!!