Comments on: Versioning Derivative Artifacts http://www.build-doctor.com/2010/01/15/versioning-derivative-artifacts/ Helping to deliver working software, one continuous integration build at a time Thu, 02 Sep 2010 12:05:37 +0100 http://wordpress.org/?v=2.8.4 hourly 1 By: Firass http://www.build-doctor.com/2010/01/15/versioning-derivative-artifacts/comment-page-1/#comment-747 Firass Mon, 18 Jan 2010 05:10:54 +0000 http://www.build-doctor.com/?p=1350#comment-747 Very nice post, and I agree with it 100%. The derived binary artifacts are of no interest to me if I can't confidently trace them back in a repeatable way to the source file that was used to generate them. When I run into an issue in production, I would like to take a look at the source files for that specific build, and if I am lucky enough to find a fix for the bug, I would like to be able to apply a patch to the same set of source files in order to generate a new binary distribution. If the build system doesn't facilitate going back and forth between source files and derived binary files, then this is a big problem waiting to happen. Very nice post, and I agree with it 100%.

The derived binary artifacts are of no interest to me if I can’t confidently trace them back in a repeatable way to the source file that was used to generate them. When I run into an issue in production, I would like to take a look at the source files for that specific build, and if I am lucky enough to find a fix for the bug, I would like to be able to apply a patch to the same set of source files in order to generate a new binary distribution.

If the build system doesn’t facilitate going back and forth between source files and derived binary files, then this is a big problem waiting to happen.

]]>