
Managing build variants with a better bootstrap
Address
Bernard D. Zelitch bzelitch@kronos.com
Bernard D. Zelitch - October 2003
Does your nightly build process change over time? Do you run several different flavors of the same build process in a given week? If either answer is yes, how do you associate a build configuration with a particular build so it is reproducible? The problem is not trivial. To explain why, I will consider a common build architecture that is simple but flawed. Then I will offer a better approach: a never-changing, universal bootstrapping file that sets up every build and logs its actions. In the examples that follow, I will use a bash shell look, anticipating that readers will be able to adjust for look and syntax.
Does your nightly build process change over time? Do you run several different flavors of the same build process in a given week? If either answer is yes, how do you associate a build configuration with a particular build so it is reproducible? The problem is not trivial. To explain why, I will consider a common build architecture that is simple but flawed. Then I will offer a better approach: a never-changing, universal bootstrapping file that sets up every build and logs its actions. In the examples that follow, I will use a bash shell look, anticipating that readers will be able to adjust for look and syntax.
Reviews (0)
Be the first to review this listing!
