# US 2021/0279050 A1 · System and method for implementing self-driven change detection release automation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0279050 A1 - Document ID: US20210279050A1 - Status: Published application - Kind: A1 - Application number: 17/192,416 - Filed: 2021-03-04 - Published: 2021-09-09 - Earliest claimed: 2020-03-04 - Assignees: JPMorgan Chase Bank, N.A. - Applicants: JPMorgan Chase Bank, N.A. - Inventors: Fei Chen - Web page: https://patentgrep.com/patent/US20210279050A1 ## CPC - G06F 8/65: Updates (security arrangements therefor G06F21/57) - G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management - G06F 9/4843: {by program, e.g. task dispatcher, supervisor, operating system} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract An embodiment of the present invention is directed to a system and method for implementing a self-driven change detection release automation. According to an embodiment of the present invention, a software release bot may be created and installed on software running environment. The bot may further detect changes on a server environment. For example, the bot may be integrated with scheduling and other tools where the bot is programmed to wake up at predetermined time intervals, e.g., 15 minutes. According to an embodiment of the present invention, the bot may handle release activities defined in the configuration, e.g., stop, start, send notification, etc. The bot is able to save release events log for change audit. ## Claims ### Claim 1 A system that implements a self-driven change detection release automation in software development life cycle, the system comprising: a memory component that stores change detection data; a user interface that receives inputs via a communication network; a system interface that is communicatively coupled to one or more servers in a server environment; and a computer processor coupled to the memory component, the user interface and the system interface and further programmed to perform the steps of: executing, via the system interface, a software release bot on the server environment; automatically detecting, via a signal received from the software release bot, one or more changes on the server environment; initiating one or more corresponding actions defined in a configuration file; wherein the corresponding actions comprise: performing a pre-check process, executing a stop application of a current version, and executing a start application of an updated version; automatically saving one or more events as an events log; performing one or more post-check validations; generating a notification of one or more release updates; and communicating, via the communication network, the notification to at least one recipient. ### Claim 2 (depends on 1) The system of claim 1, wherein the one or more changes exceed a predefined threshold. ### Claim 3 (depends on 1) The system of claim 1, wherein the software release bot handles release activities defined in the configuration file. ### Claim 4 (depends on 1) The system of claim 1, wherein the configuration file comprises release metadata. ### Claim 5 (depends on 1) The system of claim 1, wherein the software release bot generates a release events log for change audits. ### Claim 6 (depends on 1) The system of claim 1, wherein the software release bot comprises a local lightweight program that self-detects one or more changes. ### Claim 7 (depends on 1) The system of claim 1, wherein the software release bot performs one or more actions comprising: wake up local release jobs, restart software, validate change and validate process. ### Claim 8 (depends on 1) The system of claim 1, wherein the notification of one or more release updates further comprises change detection data and status information. ### Claim 9 (depends on 1) The system of claim 1, wherein the at least one recipient provides a response to the notification. ### Claim 10 (depends on 1) The system of claim 1, wherein the software release bot is integrated with a scheduling tool. ### Claim 11 A method that implements a self-driven change detection release automation in software development life cycle, the method comprising the steps of: executing, via a system interface, a software release bot on a server environment wherein the system interface is communicatively coupled to one or more servers in the server environment; automatically detecting, via a signal received from the software release bot, one or more changes on the server environment; initiating, via a computer processor, one or more corresponding actions defined in a configuration file; wherein the corresponding actions comprise: performing a pre-check process, executing a stop application of a current version, and executing a start application of an updated version; automatically saving one or more events as an events log; performing one or more post-check validations; generating a notification of one or more release updates; and communicating, via a communication network, the notification to at least one recipient. ### Claim 12 (depends on 11) The method of claim 11, wherein the one or more changes exceed a predefined threshold. ### Claim 13 (depends on 11) The method of claim 11, wherein the software release bot handles release activities defined in the configuration file. ### Claim 14 (depends on 11) The method of claim 11, wherein the configuration file comprises release metadata. ### Claim 15 (depends on 11) The method of claim 11, wherein the software release bot generates a release events log for change audits. ### Claim 16 (depends on 11) The method of claim 11, wherein the software release bot comprises a local lightweight program that self-detects one or more changes. ### Claim 17 (depends on 11) The method of claim 11, wherein the software release bot performs one or more actions comprising: wake up local release jobs, restart software, validate change and validate process. ### Claim 18 (depends on 11) The method of claim 11, wherein the notification of one or more release updates further comprises change detection data and status information. ### Claim 19 (depends on 11) The method of claim 11, wherein the at least one recipient provides a response to the notification. ### Claim 20 (depends on 11) The method of claim 11, wherein the software release bot is integrated with a scheduling tool.