CONTINUOUS SOFTWARE DEPLOYMENT
Methods and systems may be used to deploy software more quickly from development to a production environment. The methods and systems may speed up the process of developing and deploying new code. Integrations may be provided to monitor aspects of the system to provide statistics and metrics for better understanding and to automatically optimize certain aspects of the software development cycle.
1 .- 13 . (canceled)
14 . A computer-implemented method for application creation, the method comprising:
receiving a user input indicative of an application name;
receiving a user input indicative of a desire to create a new application;
receiving a user selection of a coding language;
receiving a user input indicative of an application name;
creating a repository for storing code for the new application;
configuring and enabling continuous integration for the repository to be continuously updated with code from a plurality of developers;
creating a continuous deployment pipeline for deploying code from the repository to a production release; and
initiating an application framework corresponding to the coding language,
15 . The method of claim 14 , further comprising:
creating a user entity with permissions for managing a production hardware infrastructure; and
creating tokens for secrets management.
16 . The method of claim 15 , wherein:
the permissions for managing a production hardware infrastructure includes permission to perform at least one of creating the production hardware infrastructure or disabling a production hardware infrastructure.
17 . The method of claim 15 , wherein:
the production hardware infrastructure comprises a first production hardware infrastructure and a second hardware production infrastructure.
18 . The method of claim 14 , further comprising:
creating a dashboard for displaying application performance metrics from the production release.
19 . The method of claim 18 , further comprising:
creating an automated canary deployment for the new application and maintaining or rolling back the automated canary deployment based on the application performance metrics.
20 . The method of claim 14 , further comprising:
initiating health checks for the production hardware infrastructure; and
assigning application alerts from the production release to a team selected from a plurality of teams.
21 . The method of claim 14 , further comprising:
providing a chat bot that interactively responds to requests to create an application, the chat bot triggering creation of an application in response to a user request.
22 . A non-transitory computer readable storage medium storing instructions that are executable by a computing system that includes one or more processors to cause the computing system to perform a method for application creation, the method comprising:
receiving a user input indicative of an application name;
receiving a user input indicative of a desire to create a new application;
receiving a user selection of a coding language;
receiving a user input indicative of an application name;
creating a repository for storing code for the new application;
configuring and enabling continuous integration for the repository to be continuously updated with code from a plurality of developers;
creating a continuous deployment pipeline for deploying code from the repository to a production release; and
initiating an application framework corresponding to the coding language,
23 . The non-transitory computer readable storage medium of claim 22 , wherein the instructions that are executable further cause the one or more processors to cause the computing system to further perform:
creating a user entity with permissions for managing a production hardware infrastructure; and
creating tokens for secrets management.
24 . The non-transitory computer readable storage medium of claim 23 , wherein:
the permissions for managing a production hardware infrastructure includes permission to perform at least one of creating the production hardware infrastructure or disabling a production hardware infrastructure.
25 . The non-transitory computer readable storage medium of claim 22 , wherein the instructions that are executable further cause the one or more processors to cause the computing system to further perform:
creating a dashboard for displaying application performance metrics from the production release.
26 . The non-transitory computer readable storage medium of claim 25 , wherein the instructions that are executable further cause the one or more processors to cause the computing system to further perform:
creating an automated canary deployment for the new application and maintaining or rolling back the automated canary deployment based on the application performance metrics.
27 . The non-transitory computer readable storage medium of claim 22 , wherein the instructions that are executable further cause the one or more processors to cause the computing system to further perform:
initiating health checks for the production hardware infrastructure; and
assigning application alerts from the production release to a team selected from a plurality of teams;
28 . The non-transitory computer readable storage medium of claim 22 , wherein the instructions that are executable further cause the one or more processors to cause the computing system to further perform:
providing a chat bot that interactively responds to requests to create an application, the chat bot triggering creation of an application in response to a user request.
29 . An application creation system comprising:
one or more memory devices storing processor executable instructions; and
one or more processors configured to execute the instructions to cause the application creation system to perform:
receiving a user input indicative of an application name;
receiving a user input indicative of a desire to create a new application;
receiving a user selection of a coding language;
receiving a user input indicative of an application name;
creating a repository for storing code for the new application;
configuring and enabling continuous integration for the repository to be continuously updated with code from a plurality of developers;
creating a continuous deployment pipeline for deploying code from the repository to a production release; and
initiating an application framework corresponding to the coding language,
30 . The application creation system of claim 29 , wherein the one or more processors are configured to execute the instructions to cause the application creation system to further perform:
creating a user entity with permissions for managing a production hardware infrastructure, the permissions for managing a production hardware infrastructure includes permission to perform at least one of creating the production hardware infrastructure or disabling a production hardware infrastructure; and
creating tokens for secrets management.
31 . The application creation system of claim 29 , wherein the one or more processors are configured to execute the instructions to cause the application creation system to further perform:
creating a dashboard for displaying application performance metrics from the production release.
creating an automated canary deployment for the new application and maintaining or rolling back the automated canary deployment based on the application performance metrics.
32 . The application creation system of claim 29 , wherein the one or more processors are configured to execute the instructions to cause the application creation system to further perform:
initiating health checks for the production hardware infrastructure; and
assigning application alerts from the production release to a team selected from a plurality of teams;
33 . The application creation system of claim 29 , wherein the one or more processors are configured to execute the instructions to cause the application creation system to further perform:
providing a chat bot that interactively responds to requests to create an application, the chat bot triggering creation of an application in response to a user request.