Skip to content

Monthly Archives: April 2011

Twitter Harvest, 22 April

We aimlessly browse Twitter, because we can: Continuous Integration and Feature Branches – not convinced myself, yet If 15 Engineers Deploy 25 Changesets In 24 Hours….. – these guys get it Testing Selenium IDE with Mozmill – interesting Happy Easter to all you humans out there.

Twitter Harvest, 20 April

We self-aggrandisingly  search Twitter, so you don’t want to: Continuous Deployment – Getting started is easier than you think – but harder than you want My Big Continuous Delivery Summary Post – be nice to this man, he’s on the Selenium 2 team Continuous Integration for an MMO — let’s do it! – classic Tim [...]

Twitter Harvest, 18 April

We selfishly troll Twitter, so you don’t have to: The Cure for Continuous Integration Testing: How to trim a week’s worth of testing into a day by using Bamboo Stages – that’s a lot of tests you have there Headless Testing for Continuous Integration with Git and Jasmine – VCS hooks annoy me, but testing [...]

Twitter harvest, 13 April

We selflessly search Twitter, so you don’t have to: Simple Continuous Integration / Deployment With Jenkins – Huzzah for the Debian package! Though I prefer Apache2 myself. How to Integrate Jenkins monitoring into Eclipse – Mylin integration with Jenkins. No you need never leave your IDE. Continuous Integration for SQL Server Databases – that could [...]

Jenkins talk in London, 31 May

Kohsuke Kawaguchi is doing a talk at Skills Matter, in London, on the 31st of May. You might know that he wrote Jenkins (nee Hudson). This should be a really informative talk, from someone who raised the game in Continuous Integration. I’m going to get there early to get a good seat. You need to [...]

#LondonCI gets a regular meeting

Londoners: Set the third Wednesday aside every month. We’ve got a regular meeting place and time, and now we need some speakers. I’ve started reaching out to some of the people in my address book who would make good speakers. We already have the first speaker. But please don’t let me dictate! Email me at [...]

Inform or Accommodate?

Should you stop the build when someone breaks your formatting rules? Should you detect and fix them? There were two comments on the previous post: Oliver agreed, and Will didn’t: Instead of raising errors when things like whitespace or tabs occur, why not just modify the file to correct it? After some reflection I decided [...]

Zero tolerance

This has been surprisingly useful at keeping my JS code clean. desc “Check for tabs and trailing spaces” task :crapcheck do Dir["public/**/*.js"].each do |f| next if f.match(/^lib|resources/) text = File.read(f) raise “Tabs found in #{f}” if text.match(/\t/) raise “Trailing spaces found in #{f}” if text.match(/ $| $/) end end The tab check is useful because [...]