System and method for application release orchestration and deployment

1. A system comprising:

a non-transitory memory storing instructions; and

a processor configured to execute instructions to cause the system to perform operations comprising:

collecting, via a communication platform using a system chat bot, information regarding a code release command made via the communication platform;

detecting, from the information, a request for a ticket generation for deploying a code by the system chat bot;

determining ticket attributes based in part on the request detected using the system chat bot and one or more production scripts, wherein the ticket attributes comprise a requirement for a testing and a validating of the code prior to deploying the code;

iterating a data deployment process on the code for deployment at a staging environment and a production environment based on the ticket attributes; and

deploying the code for a production of the code.

2. The system of claim 1 , wherein the data deployment process incorporates a trigger phase, a deploy phase, and a post-deploy phase.

3. The system of claim 1 , wherein the staging environment includes the testing and the validating of the code using the data deployment process.

4. The system of claim 1 , wherein the production environment includes the testing and the validating of the code using the data deployment process.

5. The system of claim 1 , wherein the determining the ticket attributes includes a communication with an automation server for a retrieval of the one or more production scripts used by the system chat bot with the request.

6. The system of claim 2 , wherein the deploy phase includes a communication with at least one of a repository manager, a monitoring system, or a service proxy.

7. The system of claim 2 , wherein the trigger phase, the deploy phase, and the post-deploy phase include notifications.

8. The system of claim 1 , wherein the data deployment process includes deploying using at least an application which can obtain an image for a container.

9. A method comprising:

collecting, via a communication platform using a chat bot, information regarding a code release command made via the communication platform;

generating, from the information, a ticket by an automation server in response to a ticket request received at the chat bot;

triggering a scheduler for a processing of a code for deployment associated with the ticket request using one or more production scripts, wherein the scheduler is triggered with a requirement from the information for a testing and a validating of the code prior to a deployment of the code;

testing the code for the deployment at a staging environment based on the requirement, wherein the testing includes a first post-deploy processing;

validating the code for the deployment at a production environment based on the requirement, wherein the validating includes a second post-deploy processing; and

deploying the code in response to the validating.

10. The method of claim 9 , wherein the staging environment includes a first data deployment process incorporating a first trigger process, a first deploy process, and a first post-deploy process.

11. The method of claim 10 , wherein the production environment includes a second data deployment process incorporating a second trigger process, a second deploy process, and a second post-deploy process.

12. The method of claim 9 , further comprising:

determining a ticket attribute associated with the ticket generated, wherein the determining the ticket attribute includes a communication with the automation server for a retrieval of the one or more production scripts used by the chat bot with the ticket request.

13. The method of claim 11 , wherein at least one of the first data deployment process or the second data deployment process includes a communication with at least one of a repository manager, a monitoring system, or a service proxy.

14. The method of claim 11 , wherein at least one of the first data deployment process or the second data deployment process include notifications.

15. The method of claim 11 , wherein at least one of the first data deployment process or the second data deployment process includes deploying using at least an application which can obtain an image for a container.

16. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:

collecting, via a communication platform using a system chat bot, information regarding a code release command made via the communication platform;

detecting, from the information, a request for a ticket generation for deploying a code by the system chat bot;

determining ticket attributes based in part on the request detected using the system chat bot and one or more production scripts, wherein the ticket attributes comprise a requirement for a testing and a validating of the code prior to deploying the code;

iterating a data deployment process on the code for deployment at a staging environment and a production environment based on the ticket attributes; and

deploying the code for a production of the code.

17. The non-transitory machine-readable medium of claim 16 , wherein the staging environment includes the data deployment process incorporating a trigger process, a deploy process, and a post-deploy process.

18. The non-transitory machine-readable medium of claim 16 , wherein the production environment includes the data deployment process incorporating a trigger process, a deploy process, and a post-deploy process.

19. The non-transitory machine-readable medium of claim 16 , wherein determining the ticket attributes includes a communication with an automation server for a retrieval of the one or more production scripts used by the system chat bot with the request.

20. The non-transitory machine-readable medium of claim 17 , wherein the data deployment process includes deploying using at least an application which can obtain an image for a container.