svn - Continuous Integration: managing configuration files targeting different environments? -
i'm setting ci our development , wanting know ideas/best practices on managing configuration files targeting different environments.
the first approach comes mind keep environment-specific configuration files in different directories under version control, , use build platform such nant copy right configuration file environment in order:
for instance, ci process follows process:
subversion -> 1. buildarea -> 2. test env -> 3. beta. env. -> 4. live
have 3 folders under version control called:
dev.config/: global.asa, app.config test.config/: gloval.asa, app.config live.config/: global.asa, app.config
and during successive steps 2, 3, 4 use nant copy right configuration file environment. perhaps might not ideal.
tools focused more on continuous delivery rather continuous integration model environments you're deploying deployment process. ones allow specific environment specific parameters, , update template configuration file (and keep secret stuff secure). think that's similar strategy puppet.
Comments
Post a Comment