FSMaxBDec 20, 2024
Lou Franco

In 2000, I read about CI/CD, but there weren’t tools yet (CruiseControl came out in 2001). So, we implemented CI by having a physical card that had to be on your desk in order to commit code. Then, you had to go over to our build (desktop) machine, get your code, run the build/test scripts (and fix if you broke them).

We eventually automated it all, but just that step saved a lot of “works on my machine” bugs from breaking our builds.

#extremeprogramming #softwareengineering

Dec 19, 2024 at 2:46pmIvory for iOS
Show threadDaniel EversDec 20, 2024
@loufranco
This reminds me of the very first "build server" I set up, around 2009(?). It started as a cron job, creating a fresh checkout (from CVS 😱) and performing a clean build every night.
Eventually it received a simple web frontend (handcrafted in Python) so you could trigger builds on demand.
Didn't take long for the decision that "we only release builds from this server" to ensure it's clean 😎.
Still, far from CI/CD ...
Show threadFSMaxBDec 20, 2024
@loufranco This reminds me of "Do nothing scripting": https://blog.danslimmon.com/2019/07/15/do-nothing-scripting-the-key-to-gradual-automation/
Do-nothing scripting: the key to gradual automation

Every ops team has some manual procedures that they haven’t gotten around to automating yet. Toil can never be totally eliminated. Very often, the biggest toil center for a team at a growing …

Dan Slimmon