Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Release It!: managing different deployment strategies

 
Gian Franco
blacksmith
Ranch Hand
Posts: 979
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

How would you suggest to manage different deployment
strategies for different customers?

E.g. some clients would like their apps deployed as
a war, others prefer loose files (!), some apps are
hosted in-house and others at the clients site.

Is this manageable with the DRY principle applied
along the line in some way?

Kind regards,

Gian
 
Michael Nygard
author
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Gian,

This is not a topic that I address in the book, but I'll give you my thoughts.

My goal with any release process is to minimize the pain involved. Painful releases just discourage people from doing them, which in turn makes the release more painful.

So, which is more painful, war files or a directory full of loose files. To my mind, the loose files are far more painful. Old files can be left around. I might run into permission or case problems on a Unix server. To avoid these, I would want to move the old directory out of the way first, which definitely requires a cleanup process after the release is done.

War files avoid several of these problems, so present less pain. I'd therefore advocate for war files.

Cheers,
-Mike
 
Gian Franco
blacksmith
Ranch Hand
Posts: 979
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Mike,

I'd advocate for war files as well, but unfortunately, due
to the working procedures of the client we are sending the
sw to, this is not possible right now.

Kind regards,

Gian
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic