Comments
Sort by recent activity
Great, thanks!
At some point I would like to use the new /include:StaticData feature because it'll help speed up our deployments. Am I going to run into the same error if I try to use that with my filter files? / comments
Great, thanks!
At some point I would like to use the new /include:StaticData feature because it'll help speed up our deployments. Am I going to run into the same error if I try to use that with my...
Hi, I apologize if my reply is untimely. We've had CI running with CruiseControl.Net for quite some time now. CCNet calls a NAnt script which does some Subversion stuff (check out the database scripts, etc.) and then calls the Redgate tools to sync the databases.
It works pretty well now, but we did run into some problems along the way. I hoped we could just sync the schema then the data, but it wasn't that simple. We eventually ended up with a 5-step process to sync the database to SVN.
I detailed the steps in another post so I won't copy it here. I'm not sure that it's the best way to do CI, but it works for us. / comments
Hi, I apologize if my reply is untimely. We've had CI running with CruiseControl.Net for quite some time now. CCNet calls a NAnt script which does some Subversion stuff (check out the database sc...
I'll check it out, thanks! / comments
I'll check it out, thanks!
We're using CruiseControl.Net and NAnt scripts to do our deployments. We have a couple CI environments that are set up to deploy whenever someone commits to Subversion.
Our staging environment is the last step before production and deployments are done a little differently. First we baseline it to match Production (by deploying Trunk; we keep trunk in sync with production) and then we deploy the entire release branch to the staging environment. Sometimes if a deployment fails or we find bugs, we need to redeploy, which involves first deploying Trunk and then deploying the branch again. I'm curious if the migration scripts will get deployed again in this scenario (we would like them to be). Update: I tested the above scenario, and it seems that the migration scripts do not get run the second time. I could probably get around this by changing the property so it reflects the first revision of the branch before we do the sync. / comments
We're using CruiseControl.Net and NAnt scripts to do our deployments. We have a couple CI environments that are set up to deploy whenever someone commits to Subversion.
Our staging environment is ...