In our team development setup, depicted in 
, we observe several developers' machines, each equipped with the previous version of GeneXus, all linked to a GeneXus Server hosting the same GeneXus version. There's also a special machine not directly used by developers but instead is automated with Jenkins for Continuous Integration purposes. This machine packages the application with pack customizations.
Subsequently, the application deployment is carried out in either a TEST environment or a production environment, each requiring its set of customizations.
The upgrade process involves several critical steps. While the sequence of these steps can vary, it's essential to complete all of them:
Upgrade Genexus in developers's machines
- Upgrade GeneXus on all developers' machines to the new version.
- Customize the GeneXus installation by adjusting the
genexus.exe.config file, used User Controls, GAM/GXFlow platforms, utilized extensions, and patterns.
- Authorize the new versions by managing licenses.
- For each Knowledge Base (KB) within the team, perform a "Create KB from Server" followed by a "Rebuild all" using the new version. Address any arising errors.
- Migrate modified and pending objects from the old KB to the new KB (work in progress).
Once no KBs remain on the old version:
- Remove the old GeneXus installation.
- Delete the old KB.
Next, focus on the server-side:
- Install a GeneXus Server with the new GeneXus version.
- Migrate/Transfer the KB from the old GeneXus Server to the new one.
- Reconnect all developer KBs to the new server.
Finally, adjust the application packaging and deployment:
- Update pack customizations on the build machine.
- Update deployment customizations on production or client machines.
By carefully following these steps, you can ensure a smooth transition to the new GeneXus version in a collaborative development environment.
Most of these tasks can be automated to achieve more organized updates to GeneXus versions.