Build system issues are testing culture issues.
4 plus ones
Shared publicly•View activity
- Are you looking at making the build more self-documenting/self-diagnosing? I lost a lot of momentum when I kept hitting opaque errors. Part of that is probably my lack of familiarity with the tools, but I think one can compensate for that in the build script. I like to"code defensively" in my build scripts by checking for required env variables, command line options, etc., failing fast, and offering advice on how to fix the problem.Jun 27, 2014
- I hadn't thought that far ahead yet; right now I'm trying to make it so anyone diving into the code can easily and repeatedly execute 'make test' while developing and have the build behave as expected. Along the way I'm learning about existing build breakages and submitting fixes for them.
That said, I wish I'd thought of the word "momentum" when writing the post. That's exactly why build issues are test-killers.
BTW, something I haven't announced yet, but I just got Solano CI set up yesterday and today as an early experiment:
https://github.com/mbland/openssl/wikiJun 27, 2014
- It is awesome that you're streamlining the build. Definitely agree that will help with adoption.
I haven't worked with Solano CI before, but it is on my list now to investigate!Jun 27, 2014
- "rebuilding and executing a test is fast and correct" -- I see what you did there; also "Third, I’m having way too much fun with this." Welcome back, Mike. We've missed you.Jun 27, 2014