The drudgery of software build maintenance

posted by Jeff | Tuesday, May 5, 2026, 9:45 PM | comments: 0

I mentioned the other day how relatively uninteresting it is to update all the things in your software projects to the latest things. Today I got knee deep in an even less interesting thing, which is the build automation stuff. The short story is that when you write code, a server sees that you committed it, builds it, and depending on how you have things set up, it may automatically deploy it somewhere. The test version of the forums works that way, for example. The real power in this is that if you send up something that ends up being broken, you can just go back to a previous build and send that up.

This is something that you generally set up once, and usually at the start of a project. I couldn't even tell you when I set up the forum stuff. Part of the current set up sends those test builds out as packages to a third-party service. That service seems to be melting down, or going out of business or something, so I've had to shift that stuff elsewhere. The reason that this is annoying is that I work with the automation stuff so infrequently that I have to partially relearn it, or lean on AI to figure out why it doesn't work.

There are people who just do this stuff for a living. That's great, but I do not enjoy it at all.


Comments

No comments yet.


Post your comment: