Containerized build steps
A method includes receiving a build request containing build step instructions from a user. The build step instructions specify a usage of containers within memory hardware for building an output container. The containers include at least one private container having private contents and/or at least one public container having public contents. The method also includes authenticating the user initiating the build request and determining whether the user is authorized to access the private containers. When the user is authenticated and authorized to access the private containers, the method includes obtaining the containers specified by the build step instructions from the memory hardware, executing the build step instructions to build the output container while using the received containers, and outputting the built output container.
1. A computer-implemented method when executed by data processing hardware causes the data processing hardware to perform operations comprising:
receiving, from a user device associated with a user, a build request comprising build step instructions specifying a series of build steps for building an output container;
executing a first build step of the series of build steps to generate a first build result;
in response to generating the first build result, executing, using the first build result, a subsequent build step of the series of build steps;
in response to the subsequent build step completing execution, determining whether the subsequent build step is a final build step in the series of build steps; and
when the subsequent build step is the final build step in the series of build steps, building the output container for the user device.
2. The method of claim 1 , wherein the build step instructions specify a usage of a private container or a public container for each build step of the series of build steps to build the output container.
3. The method of claim 1 , wherein each build step of the series of build steps comprises:
a container identifier;
an environment field; and
a dependency constraint.
4. The method of claim 3 , wherein the dependency constraint specifies a prior build step in the series of build steps that must complete execution before executing the corresponding build step.
5. The method of claim 1 , wherein the series of build steps of the build step instructions specifies both a public source and a private source to provide instructions for building the output container.
6. The method of claim 1 , wherein each build step of the series of build steps comprises a status identifier indicating an execution status for the corresponding build step.
7. The method of claim 1 , wherein one or more of the build steps in the series of build steps execute in parallel with one or more other build steps in the series of build steps.
8. The method of claim 1 , wherein the operations further comprise receiving a notification indicating that the user is authenticated and authorized to access one or more private containers identified by a respective build step.
9. The method of claim 1 , wherein executing each build step of the series of build steps uses one or more virtual machines.
10. The method of claim 1 , wherein the output container comprises a build step record indicating information associated with each build step of the series of build steps.
11. A system comprising:
data processing hardware; and
memory hardware in communication with the data processing hardware, the memory hardware storing instructions that when executed by the data processing hardware cause the data processing hardware to perform operations comprising:
receiving, from a user device associated with a user, a build request comprising build step instructions specifying a series of build steps for building an output container;
executing a first build step of the series of build steps to generate a first build result;
in response to generating the first build result, executing, using the first build result, a subsequent build step of the series of build steps;
in response to the subsequent build step completing execution, determining whether the subsequent build step is a final build step in the series of build steps; and
when the subsequent build step is the final build step in the series of build steps, building the output container for the user device.
12. The system of claim 11 , wherein the build step instructions specify a usage of a private container or a public container for each build step of the series of build steps to build the output container.
13. The system of claim 11 , wherein each build step of the series of build steps comprises:
a container identifier;
an environment field; and
a dependency constraint.
14. The system of claim 13 , wherein the dependency constraint specifies a prior build step in the series of build steps that must complete execution before executing the corresponding build step.
15. The system of claim 11 , wherein the series of build steps of the build step instructions specifies both a public source and a private source to provide instructions for building the output container.
16. The system of claim 11 , wherein each build step of the series of build steps comprises a status identifier indicating an execution status for the corresponding build step.
17. The system of claim 11 , wherein one or more of the build steps in the series of build steps execute in parallel with one or more other build steps in the series of build steps.
18. The system of claim 11 , wherein the operations further comprise receiving a notification indicating that the user is authenticated and authorized to access one or more private containers identified by a respective build step.
19. The system of claim 11 , wherein executing each build step of the series of build steps uses one or more virtual machines.
20. The system, of claim 11 , wherein the output container comprises a build step record indicating information associated with each build step of the series of build steps.