Deployment is the goal

by simpsonjulian on August 17, 2009

We get things so ass-backwards. How do we get code from development team to the end user? I’ve written an article on this subject at InfoQ. I hope you like it.

Share with the group:
  • Digg
  • del.icio.us
  • Facebook
  • DZone
  • LinkedIn
  • Slashdot
  • StumbleUpon

Related posts:

  1. One scary deployment – Bamboo giveaway preview We’ve had some entries in, and I thought I’d share...

Related posts brought to you by Yet Another Related Posts Plugin.

{ 2 comments… read them below or add one }

1 Gary September 6, 2009 at 3:28 am

Nice piece. There’s a reason why companies, and even volunteer projects, don’t instinctively want to release very frequently: experience teaches us that releases introduce bugs. The key to overcoming this resistance to frequent releases is (IMHO) comprehensive functional and non-functional testing. As all the non-developer types involved with a release gain confidence in the release process as solid, so the frequency of releases can be accelerated.

I’m not a developer, so it’s easy for me to say, but the better the dev team I’ve worked with, generally, the more time spent on testing, and vice versa. Feel free to shoot me down….

2 simpsonjulian September 6, 2009 at 11:02 pm

Gary, thanks for the comment. I wouldn’t shoot you down. The moment a dev team thinks that testing is someone else’s problem, the rot sets in. Or the build, for that matter.

Leave a Comment

You can use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Previous post: News and Stuff, August 14

Next post: 6 Big Visible Continuous Integration Tools