US 12,468,519 B2
Systems and methods for in-place application upgrades
Stuart Douglas, Orange (AU); and Jason Greene, Madison, WI (US)
Assigned to Red Hat, Inc., Raleigh, NC (US)
Filed by Red Hat, Inc., Raleigh, NC (US)
Filed on Aug. 18, 2021, as Appl. No. 17/405,357.
Prior Publication US 2023/0059134 A1, Feb. 23, 2023
Int. Cl. G06F 9/44 (2018.01); G06F 8/61 (2018.01); G06F 8/65 (2018.01); G06F 8/71 (2018.01); G06F 9/455 (2018.01)
CPC G06F 8/65 (2013.01) [G06F 8/62 (2013.01); G06F 8/71 (2013.01); G06F 9/45558 (2013.01); G06F 2009/45562 (2013.01); G06F 2009/45591 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method, comprising:
obtaining source code indicating one or more dependencies;
obtaining automated tests from a repository server system to perform validation in a production environment separate from the repository server system;
generating a software application based on the source code, wherein the software application is validated based on executing the automated tests and the software application comprises the automated tests;
deploying the software application to the production environment, the software application comprising the automated tests such that the automated tests obtained from the repository server system separate from the production environment are usable to validate the software application in the production environment;
obtaining update data indicating one or more updated dependencies configured to replace the one or more dependencies associated with the software application;
generating an updated application based on the software application and the update data such that the updated application comprises the automated tests of the software application and the one or more updated dependencies;
executing a validation process on the updated application in the production environment based on executing the automated tests of the updated application that were previously included in the software application before the software application was deployed to the production environment;
detecting that the validation process failed based on at least one error occurring during the validation process;
in response to detecting that the validation process failed, outputting a notification to obtain a version of a dependency different from the one or more updated dependencies indicated in the update data, the notification indicating the at least one error associated with the validation process that failed;
subsequent to outputting the notification, reattempting the validation process of the updated application updated to comprise the version of the dependency different from the one or more updated dependencies, the validation process reattempted using the automated tests of the updated application; and
executing, based on the validation process being successful, the updated application in the production environment.