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!

Over the last few months, I've been working with a 4-H member to develop and build a smart, simple, and elegant web-application for 4-H members to upload photos they take while participating in a youth conference. Since I'm working with a 4-H member to develop the website, everything needs to have a focus on education, and I need to spend as little time as possible fussing with the infrastructure side of things, since that's not what we're focusing on. I decided that we should make a system using my self-hosted GitLab and Jenkins instances to automagically deploy changes so that the youth doesn't have to learn how that's done, and fight with the server all the time!

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

I'm finally getting around to setting up some CI/CD systems for my self-hosted GitLab server... About Time! CI/CD, Dev Ops, Pipelines, Workflows, Automated Deployment