Automated deployment of changes to applications on a cloud computing platform

Patent metadata

Field	Value
Publication number	US-12164898-B2
Application number	US-202117173537-A
Country	US
Kind code	B2
Filing date	Feb 11, 2021
Priority date	Feb 11, 2021
Publication date	Dec 10, 2024
Grant date	Dec 10, 2024

Abstract

In some implementations, a system may receive code for a package to be deployed on a cloud computing platform. The system may cause the cloud computing platform to build the package from the code. The system may install the package on the cloud computing platform in a first non-production environment, wherein the first non-production environment is a development environment. The system may automatically test the package in the first non-production environment based on first testing information for the first non-production environment in a configuration file associated with the code. The system may deploy the package on the cloud computing platform in a production environment. The system may automatically test the package in the production environment based on second testing information for the production environment in the configuration file.

First claim

What is claimed is:

1. A system for deploying an updated software package on a cloud computing platform, the system comprising:
one or more memories; and one or more processors, communicatively coupled to the one or more memories, configured to:
receive, from a version control system storing source code for a software package deployed on the cloud computing platform, updated code including one or more changes to the source code;
cause, based on receiving the updated code, a build system to initiate an automated build procedure for the updated code,
wherein a configuration file, that includes information associated with controlling the automated build procedure, is stored on the version control system;
perform first authentication of the build system with the cloud computing platform for a package registration environment,
wherein the first authentication comprises performing a local checkout of a particular authentication key associated with the package registration environment,
wherein the particular authentication key is valid for a particular span of one or more actions being performed in the package registration environment,
wherein the particular span of the one or more actions being performed includes at least one of building, installing, or testing,
wherein the particular authentication key is deleted when the particular span of the one or more actions ends, to prevent a copy of the particular authentication key from remaining after the particular span of the one or more actions being performed ends, and
wherein the authentication is performed in an ephemeral environment that is destroyed when the particular span of the one or more actions being performed ends;
build, based on the first authentication, an updated package corresponding to the updated code in the package registration environment on the cloud computing platform;
perform second authentication of the build system with the cloud computing platform for one or more non-production environments;
automatically deploy, based on the second authentication, the updated package on the cloud computing platform in each of the one or more non-production environments and test the updated package in each of the one or more non-production environments based on respective testing information for each of the one or more non-production environments in the configuration file associated with the updated code;
perform third authentication of the build system with the cloud computing platform for a production environment; and
automatically deploy, based on the third authentication, the updated package on the cloud computing platform in the production environment and test the updated package in the production environment based on testing information for the production environment in the configuration file.

2. The system of claim 1 , wherein the one or more processors are further configured to:
perform linting of the updated code based on linting rules identified in the configuration file.

3. The system of claim 1 , wherein the one or more processors are further configured to:
perform static scanning of the updated code using one or more static code scanners identified in the configuration file.

4. The system of claim 1 , the one or more processors, when performing the first authentication, are configured to:
determine, based on an account credential, secrets management system authentication information and platform information for the package registration environment;
authenticate with a secrets management system using the secrets management system authentication information;
receive, from the secrets management system, an authentication key; and
authenticate the build system with the cloud computing platform for the package registration environment using the authentication key and based on the platform information for the package registration environment.

5. The system of claim 1 , wherein the one or more processors, when automatically deploying the updated package on the cloud computing platform and testing the updated package, are configured to:
for each environment of the one or more non-production environments and the production environment:
install the updated package on the cloud computing platform in the environment;
perform unit testing on the updated package in the environment based on unit testing information for the environment in the configuration file; and
perform integration testing on the updated package in the environment based on integration testing information for the environment in the configuration file.

6. The system of claim 1 , wherein the one or more processors, when automatically deploying the updated package on the cloud computing platform in each of the one or more non-production environments and testing the updated package in each of the one or more non-production environments, are configured to:
deploy the updated package on the cloud computing platform in a first non-production environment, wherein the first non-production environment is a development environment;
test the updated package in the first non-production environment based on first testing information for the first non-production environment in the configuration file;
deploy the updated package on the cloud computing platform in a second non-production environment, wherein the second non-production environment is a quality assurance environment or a user acceptance test environment; and
test the updated package in the second non-production environment based on second testing information for the second non-production environment in the configuration file.

7. The system of claim 6 , wherein the second non-production environment is the quality assurance environment, and the one or more processors, when automatically deploying the updated package on the cloud computing platform in each of the one or more non-production environments and testing the updated package in each of the one or more non-production environments, are further configured to:
deploy the updated package on the cloud computing platform in a third non-production environment, wherein the third non-production environment is the user acceptance test environment; and
test the updated package in the third non-production environment based on third testing information for the third non-production environment in the configuration file.

8. The system of claim 1 , wherein the one or more processors are further configured to transmit a change order to a change management system, and receive, from the change management system, an automated approval or rejection based on the change order, and
wherein the one or more processors, when automatically deploying the updated package on the cloud computing platform in the production environment, are configured to:
deploy the updated package in the production environment based on receiving the automated approval from the change management system.

9. The system of claim 1 , wherein the one or more processors are further configured to:
assign a release identifier to the updated code in the version control system based on deploying the updated package in the production environment.

10. The system of claim 1 , wherein the one or more processors are further configured to:
communicate, with the cloud computing platform, to build the updated package on the cloud computing platform; and
receive, from the cloud computing platform and based on building the updated package on the cloud computing platform, an identifier associated with a package artifact related to the updated package built on the cloud computing platform.

11. The system of claim 1 , wherein the one or more processors are further configured to:
generate change orde

Assignees

• Capital One Services Llc

Inventors

• Wallis Shawn
• Wright Robert
• Torres Giovanni

Classifications

• G06F11/3698

  Environments for analysis, debugging or testing of software · CPC title

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04L63/0876

  based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title

• G06F8/61

  Installation · CPC title