The mind is like a parachute. If it doesn't open, you're meat.

VAR's Build Rules

17 Jul 2014

This is a post that came out of a discussion thread at work 1. Originally it was a simple question on alternatives to TFS as a build system. But you know how it goes, things evolve into questions you can only answer with 42.

During the conversation the rules described in this post came out of the woodwork.

Distinctions, distinctions

Before we get into the rules we need to distinguish between a build system and a build management system.

A build system performs transformations in sequence according to a predetermined dependency chain to create artifacts. A subset of this is the compilation of sources to binaries.

A build management system coordinates build system(s).

A build system is highly project specific, it is affected by toolchains, project conventions and generally can only run on a specially configured host (i.e. development environment).

A build management system can run everywhere so long as it can start the build system on the appropriate host. The specificity of a build management system is limited to the number of version control systems it supports. Although theoretically it doesn’t have to provide version control support it is a given that such support will be provided in the minimum feature set.

Jenkins, TeamCity, TravisCI, BuildBot are build management systems.

TFS tries to do both at once, mixes them up, confuses the terminology and generally does a bang up job of completely screwing things up.

VAR’s Build Rules

(var is my username at work)

1. I am the build server

Rule #1 requires that the build server follows the exact same steps as any other developer.

Expressed the other way around: Every developer has to be able to recreate locally the complete build process without deviations given the development environment and the correct version of the source tree.

2. When the build server says no, it means no!

Rule #2 says that if a build server says a build is broken, then the build is broken. Drop everything and read the logs.

There is no “it works for me”, your build server is Judge Dredd: judge, juror and executioner.

You can only adhere to this rule if you followed Rule #1

3. IDEs are the enemy AKA F5 is not a build process

Which means that if you drive your development process from an IDE there is no way you can adhere to the Build Rules.

This rule has major complications on the development environment, ties directly into the subject of allowing your developers to use whatever tools they feel comfortable with and adherence to it is actively sabotaged by Visual Studio.

My current approach to this problem is laid out in Gaudi vs. the dreaded IDE

Adhering to the rules

To create a system that adheres to rules #1 & #2 you have to think like a Lego builder: Lots of small, specialized tasks that do one thing can be used to compose more complex processes etc.

As an example a release task instead of doing everything in one big implementation will depend on the build tasks for each of the libraries and applications and the tasks that run the tests etc. Using the syntax of rake in a contrived example one would do

task :release =>[:"test:all"]

task :"test:all" => [:"test:foo", :"test:bar"]

task :"test:foo" => [:"build:foo"]

Now a developer will probably use the component tasks a lot more than the composite :release task and we will certainly have a build job on the server that only does releases.

This is a necessity since the system needs to satisfy different usage patterns: the build server uses composite tasks that implement complete workflows while the developer usex component tasks with surgical precision in the interest of speed and effectiveness.

From the perspective of the build system engineer this approach is self-evident for the same reason it’s evident when building applications: Small chunks of code are easier to manage, test, reuse and understand.

It’s also one of the reasons why make, ant and the msbuild XML syntax suck big time as general task description languages but that is a subject that requires a whole other post.

All of this segways nicely into the final rule:

4. Your (build) infrastructure is a software development project

This post has already been written

Rule #4 means you need tests and CI and a plan. To make matters worse your users are some of the most obnoxious, impatient and down right pedantic users on the face of the planet. They want everything perfect, robust, simple and fast and they want it yesterday. You better be dogfooding by this point…

1 I work at Zühlke where I have the luck to interact with brilliant engineers. Not just software engineers either.

blog comments powered by Disqus