Release Configuration Management

Question

Our editions of Windows have different sets of configuration files and binary assets for different clients. Currently, manual tuning is required before packaging and its prone to errors. What do you think about using branches for each client and creating a package / script purchasing a client branch using a trunk?

I am less versed in scalability than in ASAP auto mode.

The contents of the whole package are in SVN, but the branching and merging of SVNs are so delicate that I’m not sure that it will work sequentially in its automatic mode. If you like the idea, I can try using git-svn for this because it hopefully makes merging less delicate. We do not have to combine assets because they are organized, so the installer can simply skip inappropriate directory trees, but the configuration is not so simple.

Answer 1

, , . script ( ) .

http://automaticchainsaw.blogspot.com/2008/02/automate-config-changes-for-different.html

, , , . , , . , , , . script , script. , .

- , xml, XmlMassUpdate MSBuild. , , , .

Answer 2

, , :

#If FirstCustomer Then
   ' <code specific to the FirstCustomer version>.
#ElseIf SecondCustomer Then
   ' <code specific to the SecondCustomer version>.
#Else
        ' <code specific to other versions>.
#End If

Answer 3

, (QA, Staging, Production,...), (, , ,...) ( , , - ).

( ), . " " , script, . , , , script, . ( , ) , .

In front of your specific problem, we developed a solution based on a central configuration server that serves the configuration for clients. The server supports value inheritance, auditing and version control of changes, standardization and even runtime changes that are reset to the client in real time.

We are very close to releasing this service as a cloud-based configuration management solution. If you want to try, register for the beta version of http://woot.configchief.com