You may have deployed your application from a KB/Version/Environment and want now to deploy from another KB/Version/Environment. This article covers this case.
Scenarios in which you may want this
- The original KB got lost (Never happened to you? Congrats! :-) )
- You converted from GeneXus X Evolution 3 to GeneXus 15 and in the migration process you changed KB
- You decided to use another KB to deploy for some other reason
Note: You need GeneXus Cloud Tools build 220.127.116.11 or higher.
In the following explanation, KB0 is the KB/Version/Environment from which originally the Application was deployed. It is the one you don't want to use anymore to deploy it.
KB1 is the new one, from which you want to update the Application.
- Open KB1 and make sure the following
- That the database schema is the same as the one of the active version of the Application (KB0)
- That the properties are set with the exact same values as KB0. Take special attention when using GAM
- Build All in KB1, Test it.
- On KB1, Connect with existing application
You will be prompted for your credentials; after that, you must select the Cloud / Target and Application you want to connect to.
Select it and Connect. You will be prompted if you are sure, click YES and watch the output. If all works ok, you will get this:
========== Connect with existing Application started ==========
Connect with existing Application Success
- Now you are ready to Deploy on KB1! Follow the usual steps to update your Application.
Implementation details: The first time you deploy after connecting, a complete binaries and resources deployment is done (it's not incremental).
- If you get access to KB0, open it, go to the Preferences tab, and select the GeneXus Cloud Application you don't want anymore to deploy to from this KB and Disconnect
Do this to avoid unwanted deployments from KB0.
1) If you don't disconnect and deploy from KB0 once you deployed from KB1, you can get unexpected results and even worse: get changes to the application that are very difficult to roll back.
2) Disconnecting deletes all internal KB Versions with their links to the different Application versions. It is an action that cannot be rolled back.