Presentation given at Ruby Ireland in February 2014, detailing all of the tools that we used at the Converser startup, what they were used for and what they cost.
• develop ships to staging, automatically • feature branches arrive via reviewed pull request to develop • develop is merged to master • activity appears in hipchat
to staging on successful run • notifies hipchat on fails and recoveries in hipchat • rspec / minitest / jasmine • phantomjs and casper still human powered as part of review
/ security • used to measure improvements and encourage continuous small focussed refactors • raise security issues as bugs • does not inhibit build success
to non-technical staff (and used by same) • notifies hipchat with events - different room per broad topic area • caveat - velocity calculation ineffective for small teams
• custom categorize messages as events • set triggers based on events • automate alerts based on trigger counts • emails and send SMS messages (thru mon)