Can you deploy previous revisions in ODC without increasing the revision counter?
In Outsystems 11, using Service Center, we can see the list of revisions and manually select which revision is to be currently published without increasing revisions.
In ODC, however, it seems that for me to "rollback" to previous revisions, I would have to open the older revision in ODC Studio and then publish it (thus revision increases) as shown here:
https://success.outsystems.com/documentation/outsystems_developer_cloud/deploying_assets/rollback_apps/
This can make it harder to track revisions, or merging with newer code after performing a rollback. Any insights?
Hello @Timothy John Tee Argota ,
Based on what I know, it’s the containerization of apps and the packaging of libraries in ODC that cause this behavior. In O11, when apps are deployed, the platform compiles the .NET code and hosts the files on IIS. So if you want to revert back, the system simply swaps in the older compiled files, and that’s it. No rebuild is done, and therefore the revision number doesn’t increase.
But in ODC things are different. Because apps are containerized and libraries are packaged together with the app, a rebuild is required in every scenario. Even when you go back to an older version, ODC still needs to rebuild the code, create a new container, and package it with the current library versions. That’s why the revision number increases, even when rolling back to a previous revision.