CI and DB development part II the deploy....
Well lets see... got CruiseContorl .Net working with msbuild so not to automate the deployment to a test server...
Easy enough (as we tested this manually with MSBuild). The only change is to create a build configuration that has the CC .Net working directory as its build output path. That way when the Deploy target is selected MSBuild will know where to grab the correct sql file and use that to update the test server.
Results... so far so good. I've got it so I can update the db project, deploy it locally to test on "my box", then check it in. CC .Net takes over and pushes it to the test server.
Next is to figure out the best way to unit test it...
One approach is to create a test project and have it run the tests. The only trick is making sure it points at the right server. E.g. the developer's box when he is testing locally, then switch to the test box when CC .Net / MSBuild run the code. We'll see...
Easy enough (as we tested this manually with MSBuild). The only change is to create a build configuration that has the CC .Net working directory as its build output path. That way when the Deploy target is selected MSBuild will know where to grab the correct sql file and use that to update the test server.
Results... so far so good. I've got it so I can update the db project, deploy it locally to test on "my box", then check it in. CC .Net takes over and pushes it to the test server.
Next is to figure out the best way to unit test it...
One approach is to create a test project and have it run the tests. The only trick is making sure it points at the right server. E.g. the developer's box when he is testing locally, then switch to the test box when CC .Net / MSBuild run the code. We'll see...
posted by edgaralgernon at 11:35 AM
0 Comments:
Post a Comment
<< Home