Flag to Force a deployment
Occasionally the only changes in a specific build is the addition to the PostScript post-deployment script. Since there are no schema changes, the PostScript change is not executed.
Faking a schema change by adding a comment or something is a poor workaround in an automated CI process.
A simple flag -AlwaysRunUpgrade to always run the PreScript and PostScript as part of the deployment would be ideal.
I fully agree to this idea.
We have run in the issue this week, where expected changes to production did not happen due to this issue.
The post-script is a very usable place to enforce changes to data, for example setting defaults for a new field.
It is a common mistake that the development team first introduces a new column and forgets to set a migration script in the post-script. After a bug report, the issue is fixed in the post-script. If for some reason, there is no other change, the post script is not applied. More so, since we have 3 environments, dev, tst, prd, the redgate tool should be a trusted help, not something to work arround.
Since the postscript should be repeatable by nature, this should not be a problem to apply this every time, given it a much more stable transition to production.