Of course we’re all very aware of the possible pitfalls when deploying a new version of our application. It does happen that we run a deploy with one cup of coffee to little and miss something.
The [sf_product_info] table contains a lot of usefull information about what has been deployed, but missing in there is what previous version the deployment was based on.
We recently had an issue on a non production enviroment that we had a difficult time to diagnose and even more difficult to repair. The root cause was that the environment went from version 2.55.7 to 2.55.16 but the .16 reployment was based on the .9 version.
Would it be possible to add a sf_project_vrs_previous column to the sf_product_info table? That way we can check for constancy when deploying new versions.
Hello@Bas (and voters),
To implement this idea, I want to put this US on the backlog:
We are thinking about adding the from-version to the upgrade script and making the upgrade script or deployer check on the previous version.
I was wondering if you would see the need to store the previous version in sf_product_info, or that maybe our solution is enough to complete for your idea.
Hi@Bas ,
We would still like to hear what you think of Ester's suggestion. Looking forward to hearing from you.
Jeroen
Hi Jeroen,
sorry i was on holiday the last few weeks, Thanks for the reminder message.
The story Ester described will absolutely help. I’m wondering how this would work if your exporting the deployment script and manually running it. The client we’re working for now enables us to do direct deployments everywhere except development, those SQL script need to be deployed by the IT team.
Having the from-version in the database does help with historical overview. Only having a check when doing the upgrade would only check at that point in time.
Hello Bas,
Starting with the next release of the Thinkwise Platform, the sf_product_info table will track what the previous project and project version were when the upgrade took place.