Automated software deployment and management

1 . A system comprising:

a software release validation platform including a first electronic processor configured to:

receive a first input at a first input field of a graphical user interface,

generate a release container associated with the first input,

receive a second input at a second input field of the graphical user interface,

generate an issue and automatically associate the issue with the release container based on the second input,

receive a third input at a third input field of the graphical user interface, and

transmit a command signal in response to receiving the third input; and

a software release deployment platform including a second electronic processor configured to:

receive the command signal,

in response to receiving the command signal, access the software release validation platform and process a status of each issue of a plurality of issues associated with the release container, and

in response to the status of each issue of the plurality of issues having a completed status:

retrieve source code from a source code repository platform,

compile the source code,

deploy the compiled source code to a production platform, and

determine an effective lead time metric based on a difference between (i) a first date-time group associated with a first commit among a plurality of commits tagged to the plurality of issues associated with the release container and (ii) a second date-time group corresponding to a time at which the software release deployment platform determines that each issue of the plurality of issues has the completed status.

2 . The system of claim 1 , wherein the first input includes an identifier of a software release.

3 . The system of claim 2 , wherein the second input includes the identifier of the software release.

4 . The system of claim 3 , wherein the source code is tagged with the identifier of the software release.

5 . The system of claim 4 , wherein:

the source code repository platform includes the plurality of commits tagged to the issue; and

each commit includes source code.

6 . The system of claim 5 , wherein the retrieved source code is associated with a commit tagged to the issue.

7 . The system of claim 1 , wherein the first electronic processor is configured to:

generate a message containing the effective lead time metric; and

transmit the message to a stakeholder device.

8 . A method comprising:

receiving, with a software release validation platform, a first input at a first input field of a graphical user interface;

generating, with the software release validation platform, a release container associated with the first input;

receiving, with the software release validation platform, a second input at a second input field of the graphical user interface;

generating, with the software release validation platform, an issue and automatically associating the issue with the release container based on the second input;

receiving, with the software release validation platform, a third input field at a third input field of the graphical user interface;

transmitting, with the software release validation platform, a command signal in response to receiving the third input;

receiving, with a software release deployment platform, the command signal;

accessing, with the software release deployment platform, the software release validation platform and processing a status of each issue of a plurality of issues associated with the release container in response to receiving the command signal; and

in response to the status of each issue of the plurality of issues having a completed status:

retrieving, with the software release deployment platform, source code from a source code repository platform,

compiling, with the software release deployment platform, the source code,

deploying, with the software release deployment platform, the source code to a production platform, and

determining an effective lead time metric based on a difference between (i) a first date-time group associated with a first commit among a plurality of commits tagged to the plurality of issues associated with the release container and (ii) a second date-time group corresponding to a time at which the software release deployment platform determines that each issue of the plurality of issues has the completed status.

9 . The method of claim 8 , wherein the first input includes an identifier of a software release.

10 . The method of claim 9 , wherein the second input includes the identifier of the software release.

11 . The method of claim 10 , wherein the source code is tagged with the identifier of the software release.

12 . The method of claim 11 , wherein:

the source code repository platform includes the plurality of commits tagged to the issue; and

each commit includes source code.

13 . The method of claim 12 , wherein the retrieved source code is associated with a commit tagged to the issue.

14 . The method of claim 8 , further comprising:

generating, with the software release validation platform, a message containing the effective lead time metric; and

transmitting, with the software release validation platform, the message to a stakeholder device.