Automated deployment of continuous integration
The technology disclosed herein enables identifying, in a container registry, a plurality of containers corresponding to a plurality of continuous integration (CI) components for continuous integration, deploying, to an execution environment, the plurality of containers, identifying, based on a configuration script, a dependency between a first container of the plurality of containers and a second container of the plurality of containers, and configuring, based on the dependency, the second container to access data of the first container. Each container of the plurality of containers corresponds to a CI component of the plurality of CI components.
1. A method comprising:
identifying, in a container registry, a plurality of containers corresponding to a plurality of continuous integration (CI) components for continuous integration;
deploying, to an execution environment, the plurality of containers, wherein each container of the plurality of containers corresponds to a CI component of the plurality of CI components;
identifying, based on a configuration script, a dependency between a first container of the plurality of containers and a second container of the plurality of containers; and
configuring, based on the dependency, the second container to access data of the first container.
2. The method of claim 1 , wherein each of the plurality of CI components is one of: an execution method type component, a data routing type component, a test analysis type component, or a reporting type component.
3. The method of claim 1 , wherein identifying, based on a configuration script, a dependency between the first container of the plurality of containers and the second container of the plurality of containers comprises determining that the second container utilizes a result produced by the first container.
4. The method of claim 1 , wherein identifiers of the plurality of CI components received via one of: a user interface (UI), an application programming interface (API), or remote protocol command (RPC).
5. The method of claim 1 , wherein the configuration script defines a corresponding dependency for each container of the plurality of containers.
6. The method of claim 1 , wherein identifying the plurality of containers based on the plurality of CI components comprises:
for each CI component of the plurality of CI components, identifying, in the container registry, a container associated with a label of a respective CI component.
7. The method of claim 1 , wherein the container registry comprises at least one of: a global container registry, a local container registry, or an image storage.
8. The method of claim 1 , further comprising:
providing a user interface access to the execution environment.
9. The method of claim 1 , wherein the execution environment comprises at least one of: a local execution environment or a cloud execution environment.
10. A system comprising:
a memory; and
a processing device, operatively coupled to the memory, the processing device to:
identify, in a container registry, a plurality of containers corresponding to a plurality of continuous integration (CI) components for continuous integration;
deploy, to an execution environment, the plurality of containers, wherein each container of the plurality of containers corresponds to a CI component of the plurality of CI components;
identify, based on a configuration script, a dependency between a first container of the plurality of containers and a second container of the plurality of containers; and
configure, based on the dependency, the second container to access data of the first container.
11. The system of claim 10 , wherein each of the plurality of CI components is one of: an execution method type component, a data routing type component, a test analysis type component, or a reporting type component.
12. The system of claim 10 , wherein, to identify, based on a configuration script, a dependency between the first container of the plurality of containers and the second container of the plurality of containers, the processing device is to determine that the second container utilizes a result produced by the first container.
13. The system of claim 10 , wherein identifiers of the plurality of CI components via one of: a user interface (UI) or an application programming interface (API).
14. The system of claim 10 , wherein the configuration script defines a corresponding dependency for each container of the plurality of containers.
15. The system of claim 10 , wherein, to identify the plurality of containers based on the plurality of CI components, the processing device is to:
for each CI component of the plurality of CI components, identify, in the container registry, a container associated with a label of a respective CI component.
16. The system of claim 10 , wherein the container registry comprises at least one of: a global container registry or a local container registry.
17. The system of claim 10 , wherein the processing device is further to:
provide a user interface access to the execution environment.
18. The system of claim 10 , wherein the execution environment comprises at least one of: a local execution environment or a cloud execution environment.
19. A non-transitory computer-readable storage medium storing instructions that, when executed by a processing device, cause the processing device to:
identify, in a container registry, a plurality of containers corresponding to a plurality of continuous integration (CI) components for continuous integration;
deploy, to an execution environment, the plurality of containers, wherein each container of the plurality of containers corresponds to a CI component of the plurality of CI components;
identify, based on a configuration script, a dependency between a first container of the plurality of containers and a second container of the plurality of containers; and
configure, based on the dependency, the second container to access data of the first container.
20. The non-transitory computer-readable storage medium of claim 19 , wherein each of the plurality of CI components is one of: an execution method type component, a data routing type component, a test analysis type component, or a reporting type component.