90% sure this is operator error: I have an Octopus Deploy release process that includes the IgnoretSQLt option in the deployment. Octopus is deploying from a Team City created package from a SQL Source Control project. The changes deploy but the deployment ultimately "fails" on the post-update schema check when the tSQLt objects aren't in the database?
Comments
1 comment
-
Hello @josh_smith
Thanks for posting.
It looks like this will require some investigation. If you have a current support and upgrades contract, please reach out to our support team who will be happy to help.
Add comment
Please sign in to leave a comment.