Hi ,
I know the recommended way of doing the hot fixes by Outsystems is this.
But we have a need of making the dev environment as same as Production during the time of hot fixing if any prod bug occurs.
My client asked if this is possible:
When we deploy release, make a new module which is copy of existing deployed module, say ADJ Core 1.0 went to Prod, we make new modulecADJ Core Backup 1.0 at that time.
New sprint work begins by modifying 1.0. Say it becomes 2.0 while we are planning next release. At this point we get Prod Ticket and we need to deploy hotfix.
For this you modify “ADJ Core Backup 1.0”. Deploy this to Dev, make changes, push to QA and then to Prod (it becomes ADJ Core Backup 1.1).
Whatever was in Development/QA before starting hotfix is still intact in component ADJ Core 2.0 at this point.
Now to resume back, you manually apply hotfix changes in 2.0 (unless OS provides compare and merge tool for components), deploy it to Dev/QA. And make another new component “ADJ Core Backup 1.2” (in prep for future hotfix), delete “ADJ Core Backup 1.1”
is this possible?
Hi Yamini,
The best scenario would be having an additional environment mirroring Production version, where you could apply hotfixes directly and deploy them to Production.
If you don't have an extra environment to do as above, you'll have to somewhat do as the Client suggested.
An hotfix scenario that would match the Client's recommendation is the following:
1. Create a solution package in Production with the modules that are the team intends to hotfix;
2. Download the solution's current version from PRD;
3. Install the solution package in QA;
4. Apply the hotfix in QA;
5. Deploy the changes from QA to PRD;
6. Apply the hotfix in DEV;
7. Deploy from DEV to QA.
This ensures the hotfix is applied in all environments while keeping the current sprint's version in DEV.
Hope this solves the issue.
Regards,
Diogo