Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I am in charge of the deployment or implementation work.Due to my company's immaturity product,there is a version upgrade serveral days.

Each time there is a upgrade version,I had to notify the customer they had to replace their old version product.What I do is reconfigure all the configuration files for different customers who has its specific needs. Finally email them the new version of products and tell them ...

Doing all this work is boring. Is there anyone have similar experiences? Any advice is welcomed.

More context: I get a updated version from svn respository,it's configuration files is default.And each customer needs serveral configuration files different from each other,but their own configuration files is normally stay unchanged.My work is to export serveral products from the svn folder for each customer and copy their own configuration files in.

share|improve this question
5  
Could you add more detail what kind of software you are deploying, and what languages, frameworks, build-systems, or version-control you are using? Because there are many different ways to try to automate it, depending on those factors. –  Darien Aug 3 '11 at 6:55
    
Every upgrade alters the config file or is it unnecessarily over-writing it with default settings? –  JeffO Aug 3 '11 at 12:37

2 Answers 2

up vote 8 down vote accepted

This is not "version nightmare". It is un-automated deployment.

In principle you are creating a new version every time a developer checks in new changes. It should be possible to send this version to customers (but if it does not pass QA it shouldn't, naturally).

Most modern systems have an auto-update facility which allows the users to update their software to a newer version either automatically or when they press the update-button. Perhaps this might be an interesting approach if the manual deployments are too cumbersome.

In any case, any tedious, repetitive task which could be automated should probably be considered to be automated. You really want that single-button-press deployment.

share|improve this answer

reconfigure all the configuration files for different customers who has its specific needs. Finally email them the new version of products and tell them ...

Couldn't this be completely automated? Make a script that takes all customers' needs and email addresses from some kind of database, creates the configuration files according to the each customer's specific needs, packages the product separately for each customer, and emails it to them?

Python is a good language for this kind of systems.

share|improve this answer
1  
+1: Yes, it should be automated. –  Spoike Aug 3 '11 at 7:29

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.