Configurable Builds: One configuration file per user
Following on from my first post about making builds configurable, the second way of doing this that I have seen is to have one configuration build file per user.
This approach is more useful where there are different configurations needed on each developer machine. For example, if the databases being used for development are on a remote server then each developer machine would be assigned a database with a different name.
The setup is fairly similar to configuring by environment - the main difference is that we don’t have to pass the user in as a parameter. The following would go near the top of the build file:
<property name="user" value="${environment::get-user-name()}" />
<include buildfile="${trunk.dir}\config\${user}.properties.xml" />We can then have different configurations for two developer machines like so:
developer1.properties.xml
<?xml version="1.0" ?>
<properties>
<property name="property1" value="onevalue" />
</properties>developer2.properties.xml
<?xml version="1.0" ?>
<properties>
<property name="property1" value="anothervalue" />
</properties>We can then run the build file like this:
nant -buildfile:build-file.build target-nameThe disadvantage of this approach is that every time a new developer joins the team they need to create a new configuration file with their settings in. We also need to ensure that the continuous integration build is running using an independent user account. It provides more flexibility and is easier to setup on the plus side.
My colleague Jim Barritt points out a similar technique his team is using here.
About the author
I'm currently working on short form content at ClickHouse. I publish short 5 minute videos showing how to solve data problems on YouTube @LearnDataWithMark. I previously worked on graph analytics at Neo4j, where I also co-authored the O'Reilly Graph Algorithms Book with Amy Hodler.