Deploying from source control
This is just a quick note for public review, you are probably aware that I am doing deployments by doing a "svn up && build". I am now thinking about how we can apply the same idea to deploying DSL. This ensures, at the very least, that our DSL are under source control. But that has led me to another thought, if we are enforcing SCM for the DSL, why not enforce unit testing as well?
Part of the loading process of a DSL can be loading the DSL and its unit tests, executing the unit tests and only accepting them if they all passed. Failure in the unit tests or lack of unit tests would cause the DSL load process to fail.
Thoughts?
Comments
Absolutely. My deployments have started to do the same thing.
I had been thinking this as well.
The way I'm starting to use DSL's is that instead of n 'configuration tables' that store setttings about which rules to load into an object is that the dsl would replace that, so naturally it has to come from somewhere and using a vcs seems better to me than pulling it from the database or just a plain old file system.
Comment preview