I am trying to understand whether database upgrades run within a CI/CD setup.
On my local machine i upgrade my version of Umbraco via Nuget and when i browse to the site it asks me to login so the system can upgrade. Once completed the web config gets the new version of Umbraco inserted into it.
This then gets pushed into our CI (TeamCity) and then CD (OctopusDeploy). When it gets pushed to the next environment because the web config has already been updated i do not get the upgrade screens.
It should upgrade you still, but silently. You'll have the more advanced version number in the web.config and the latest files. It's only the DB that will be out of date. Because DB changes are generally done via migrations (https://cultiv.nl/blog/using-umbraco-migrations-to-deploy-changes/), any migrations should fire to complete the business when each new migration realises that it hasn't been run yet.
Old topic, but still relevant; it seems there is no check for DB migrations if the version number in the web.config is up-to-date.
I just checked this going from 8.5.5 to 8.6.1 and I no DB migrations were run on the staging environment.
Database upgrading with CI/CD
Hi Community,
I am trying to understand whether database upgrades run within a CI/CD setup.
On my local machine i upgrade my version of Umbraco via Nuget and when i browse to the site it asks me to login so the system can upgrade. Once completed the web config gets the new version of Umbraco inserted into it.
This then gets pushed into our CI (TeamCity) and then CD (OctopusDeploy). When it gets pushed to the next environment because the web config has already been updated i do not get the upgrade screens.
Does this mean the DB will not get updated ?
It should upgrade you still, but silently. You'll have the more advanced version number in the web.config and the latest files. It's only the DB that will be out of date. Because DB changes are generally done via migrations (https://cultiv.nl/blog/using-umbraco-migrations-to-deploy-changes/), any migrations should fire to complete the business when each new migration realises that it hasn't been run yet.
I can't be certain though. Sorry.
Thanks David for pointing me in the right direction, nice article :)
Old topic, but still relevant; it seems there is no check for DB migrations if the version number in the web.config is up-to-date.
I just checked this going from 8.5.5 to 8.6.1 and I no DB migrations were run on the staging environment.
is working on a reply...