Testing, Release Engineering, CI - building code that deploys and runs like it should.

Lately I've been working on creating SVN repos of code I've done in the past. Doing so makes me realize again how hard release engineering can be.

Here is a look at the problem from Wez Furlong that details what release engineering is all about: Release Engineering

The first setup in proper release engineering, is selecting your build tools. And boy is that a HARD thing to do these days.

There are about a million different ways to compile, link, and build things. Every platform has it's own problems and custom switches needed to get the job done right.

Just look at some of the tools we have to choose from when we are looking for a cross platform build manager:
Bakefile, CMake
,Autoconf and Automake
Autotools Tutorial

HUBOT - github has developed a chat bot to interact with operations. Modeled after GitHub's Campfire bot, hubot. extendable with community scripts and your own custom scripts, and can work on many different chat services.

Voices against TDD

Some funny..

Web Resources

Javascript Continuous Integration Testing

CruiseControl.net

MSBuild

Functional Testing

Continuous Integration Server

Things related to unit testing

Mocking frameworks

Usability testing

Code review

Code analysis

msi Microsoft installation stuff

travis-ci

Jenkins

import hudson.model.*

hudson.model.Hudson.instance.items.findAll{job -> job}.each {
job ->
println("Job: " + job.name)
}

Gradle

Versioning, setting uniquely identifying your build outputs

Capistrano for deployment

Puppet

Puppet and MCollective

Puppet and Augeas

augeas { "display_errors":
    context => "/files/etc/php5/apache2/php.ini",
    changes => "set PHP/display_errors Off",
}

Cucumber

Ruby testing

Software Verification

local browser syncs