Hey guys,
So, I was just thinking, we're going to be trying to make a build server on TeamCity and then using Continuous Integration push to Octopus Deploy so we can automate deployments, checks and push to testing and production.
One thing that may trip us up is if someone pushes up some changes to our source control that would not include a migration if they've altered the schema of their EF models.
Obviously, once we push the changes to our source control it will bring it down and build, and hopefully push automatically to the Testing environment.
Now, I haven't checked this, but I'd like to be able to say if it's doing a Debug build then do DropAndRecreate, and if it's release, do the migrations as necessary and push up.
Is there a blocker on the DropAndRecreate if you have migrations on, or is there a tool in place we can put into our Build Server that will look at the migrations generated, check the schema and fail the build.
We wouldn't want the build server generating the migration because then it wouldn't be saved in the source control, but if it could fail the build if it's obviously wrong then that would be a good solution.