I was able to get this to work with the exception of Migration Scripts. My scenario was similar, but using Bamboo instead of Team City.
Basically this:
Bamboo:
- Monitor Git for changes
- Get latest source for branch
- Build database (validate) and create NuGet package
- Push to Octopus
- Create a release in Octopus
Octopus:
- Install package
- Redgate - Create Database Release (step template imported into step template library)
- Redgate - Deploy from Database Release (another step template imported in)
- Notify
Everything works fine from the schema and populate with static data, but the migration script I added doesn't get executed.
It seems there have been some changes in V5 since V4 (below is in the V4 documentation):
The current migrations feature isn't compatible with distributed version control systems like Git. However, SQL Source Control 5, add support for Git, as well as branching and merging.
Download the SQL Source Control 5
Scripts created using a previous beta version of migrations won't be compatible with SQL Source Control 5. To learn more, see Upgrading from old versions of migration scripts.
https://documentation.red-gate.com/disp ... on+scripts
I'm using Git so it sounds like it isn't supported, which is fine so I upgraded to V5. But then I found some information that seems to point it not being supported with the DLM automation tools (although it was in V4 by passing SQL Compare options, UseMigrationsV2):
Deploying migration scripts
SQL Compare 11 or later can generate deployment scripts with migrations using the following source/target types:
We recommend using SQL Compare to deploy changes to production, as you have the opportunity to review the deployment script before it's deployed. For a full walkthrough of the deployment process using SQL Compare, see Migration script examples.
It is possible to use the Get latest function in SQL Source Control to deploy these changes, however we don't recommend linking your production database directly to source control.
So it's saying you need to use "SQL Compare 11 or later" to generate deployment scripts with migrations. That to me implies that it can't be done with the DLM tools that are used by Octopus.
Maybe someone at RedGate could confirm this?
Thanks,
Dave / comments
- Community
- DLM Automation
- Can't deploy Migration Script - SQL Compare & Octopus Deploy
I was able to get this to work with the exception of Migration Scripts. My scenario was similar, but using Bamboo instead of Team City.
Basically this:
Bamboo:
- Monitor Git for changes
- Get lat...
0 votes
