Comments
1 comment
-
Hey dlaws2,
Thanks for contacting us!
Typically users put the app code in a folder parallel to the db code folder within the repository - that way the versioning is done in such a way that it will give you a good idea about what changes (app and db) were made around the same period and under the same version.
You would need to deploy app changes to your QA/UAT environments using CI software such as TFS/TeamCity/Bamboo/Jenkins and then to prod using a release management software such as Octopus Deploy/TFS/Bamboo - so essentially you can do it parallel to your db code but just in an app pipeline instead of a db pipeline.
Personally I really like using TeamCity and Octopus Deploy together - that should be a decent start guide for automating app deployments.
some various documentation below:
https://octopus.com/docs/getting-started
https://octopus.com/docs/api-and-integration/teamcity
https://confluence.jetbrains.com/display/TCD10/Continuous+Integration+with+TeamCity
https://blog.jetbrains.com/teamcity/2015/11/automating-deployments-with-teamcity-and-octopus-deploy/
https://confluence.jetbrains.com/display/TCD10/Continuous+Integration+with+TeamCity
Add comment
Please sign in to leave a comment.
All the Redgate examples I've seen online always understandably demonstrate how to source control, commit and deploy DB changes. However I have not found anything that demonstrates how one would deploy db changes and dependent code changes.
I have many sites and a few databases, many of the sites share one or more databases. All my sites live under c:/webapps/site.one.com, c:/webapps/site.two.com and so on. The databases live on d:/db/db_a, d:/db_b etc.
If I make changes to my web code and I have associated db code changes what can I use in order to create a builds that will deploy my code and db changes together?