Tool registry for DevOps toolchain automation

1. A method for configuring a DevOps job comprising:

receiving submission of a DevOps tool from a user;

receiving tool authentication information and receiving tool configuration data, including compliance information, associated with the DevOps tool through an interface from the user;

receiving platform information for a platform including a profile of resources of the platform and security group settings;

storing the DevOps tool in a tool registry that includes a vault and a database, including storing a tool token representative of the authentication information in the vault and storing the tool configuration data, including the compliance information, and the platform information in the database;

subsequent to storing the DevOps tool in the tool registry, receiving a selection of the DevOps tool for inclusion in the DevOps job along with one or more other DevOps tools to be implemented on the platform;

in response to receiving the selection, automatically and without further user intervention:

accessing the DevOps tool from the tool registry including accessing the tool token representative of the authentication information from the vault and accessing the tool configuration data, including the compliance information and platform information, from the database;

configuring the DevOps tool on the platform in accordance with the accessed authentication information and accessed tool configuration data, including the compliance information and platform information, as part of the DevOps job and for interaction with the one or more other DevOps tools; and

deploying the DevOps job deploying the DevOps job multiple times across various clouds, tools and environments.

2. The method of claim 1 , wherein receiving submission of a DevOps tool from a user comprises receiving submission of the DevOps tool from a first user; and

wherein receiving a selection of the DevOps tool for inclusion in the DevOps job comprises receiving the selection of the DevOps tool from a second user, wherein the second user is different than the first user.

3. The method of claim 1 , wherein receiving tool configuration data associated with the DevOps tool comprises receiving one or more of: tool compliance data, tool licensing data, tool contact data, tool owner data, project data, application data, tool create configuration metadata.

4. The method of claim 1 , wherein configuring the DevOps tool comprises configuring the DevOps tool for a first pipeline.

5. The method of claim 4 , further comprising:

subsequent to configuring the DevOps tool for a first pipeline, receiving a further selection of the DevOps tool for inclusion in a second pipeline;

in response to receiving the further selection, automatically and without further user intervention:

again accessing the DevOps tool from the tool registry including accessing the authentication information from the vault and accessing the tool configuration data from the database; and

configuring the DevOps tool in accordance with the accessed authentication information and accessed tool configuration data for the second pipeline.

6. The method of claim 1 , wherein receiving submission of a DevOps tool from a user comprises receiving submission of a DevOps tool directed to one or more DevOps initiatives selection from among: plan, create, verify, package, release, configure, monitor, or version control.

7. The method of claim 1 , wherein receiving submission of a DevOps tool from a user comprises receiving submission of a DevOps tool in a category selected from among: configuration management, continuous integration, source control, build tools, containerization, continuous verification, quality and testing, monitoring, logging, security, static code analysis, dynamic code scanning, threat vulnerability management, container scanning, or continuous deployment and continuous delivery.

8. The method of claim 1 , wherein receiving tool authentication information comprises receiving a token; and

wherein configuring the DevOps tool in accordance with the accessed authentication information comprises validating the token.

9. The method of claim 1 , wherein configuring the DevOps tool comprises determining one or more of: dependencies, sequence, and compatibility between the DevOps tool and the one or more other DevOps tools.

10. The method of claim 1 , wherein configuring the DevOps tool comprises configuring the DevOps tool to use both on-premise resources of the user and cloud resources of a cloud service provider.

11. A system comprising:

a processor;

system memory coupled to the processor and storing instructions configured to cause the processor to:

receive submission of a DevOps tool from a user;

receive tool authentication information and receiving tool configuration data, including compliance information, associated with the DevOps tool through an interface from the user;

receive platform information including dependency, sequence, and compatibility of the DevOps tool with respect one or more other DevOps tools for a platform and resources of the platform;

store the DevOps tool in a tool registry that includes a vault and a database including storing a tool token representative of the authentication information in the vault and storing the tool configuration data, including the compliance information, and the platform information in the database;

subsequent to storing the DevOps tool in the tool registry, receive a selection of the DevOps tool for inclusion in a DevOps job along with the one or more other DevOps tools for the platform;

in response to receiving the selection, automatically and without further user intervention:

access the DevOps tool from the tool registry including accessing the tool token representative of the authentication information from the vault and accessing the tool configuration data, including the compliance information and platform information, from the database;

configure the DevOps tool on the platform in accordance with the accessed authentication information and accessed tool configuration data, including the compliance information and the platform information, as part of the DevOps job and for interaction with the one or more other DevOps tools; and

deploy the DevOps job.

12. The system of claim 11 , wherein instructions configured to receive submission of a DevOps tool from a user comprises instructions configured to receive submission of the DevOps tool from a first user; and

wherein instructions configured to receive a selection of the DevOps tool for inclusion in the DevOps job comprise instructions configured to receive the selection of the DevOps tool from a second user, wherein the second user is different than the first user.

13. The system of claim 11 , wherein instructions configured to receive tool configuration data associated with the DevOps tool comprises instructions configured to receive one or more of: tool compliance data, tool licensing data, tool contact data, tool owner data, project data, application data, tool create configuration metadata.

14. The system of claim 11 , wherein instructions configured to configure the DevOps tool comprise instructions configured to configure the DevOps tool for a first pipeline.

15. The system of claim 14 , further comprising instructions configured to:

subsequent to configuring the DevOps tool for a first pipeline, receive a further selection of the DevOps tool for inclusion in a second pipeline;

in response to receiving the further selection, automatically and without further user intervention:

again access the DevOps tool from the tool registry including accessing the authentication information from the vault and accessing the tool configuration data from the database; and

configure the DevOps tool in accordance with the accessed authentication information and accessed tool configuration data for the second pipeline.

16. The system of claim 11 , wherein instructions configured to receive submission of a DevOps tool from a user comprise instructions configured to receive submission of a DevOps tool directed to one or more DevOps initiatives selection from among: plan, create, verify, package, release, configure, monitor, or version control.

17. The system of claim 11 , wherein instructions configured to receive submission of a DevOps tool from a user comprise instructions configured to receive submission of a DevOps tool in a category selected from among: configuration management, continuous integration, source control, build tools, containerization, continuous verification, quality and testing, monitoring, logging, security, static code analysis, dynamic code scanning, threat vulnerability management, container scanning, or continuous deployment and continuous delivery.

18. The system of claim 11 , wherein instructions configured to receive tool authentication information comprise instructions configured to receive a token; and

wherein instructions configured to configure the DevOps tool in accordance with the accessed authentication information comprise instructions configured to validate the token.

19. The system of claim 11 , wherein instructions configured to configure the DevOps tool comprise instructions configured to determine one or more of: dependencies, sequence, and compatibility between the DevOps tool and the one or more other DevOps tools.

20. The system of claim 11 , wherein instructions configured to configure the DevOps tool comprise instructions configured to configure the DevOps tool to use both on-premise resources of the user and cloud resources of a cloud service provider.