Systems and methods for building generic CI/CD pipelines
At least one application may include instructions comprising application instructions and a plurality of separate pipeline definition instructions. The application instructions may be within a virtual container including at least one program that is generically executable in a plurality of different continuous integration and delivery (CI/CD) environments. Each of the plurality of separate pipeline definition instructions may be configured for each of the plurality of different CI/CD environments such that each pipeline definition may operate only in the CI/CD environment for which it is created. Each pipeline definition may be configured to cause the CI/CD environment for which it is created to execute the at least one program.
1. A method of deploying at least one generic pipeline, the method comprising:
creating, by a processor, a virtual container including at least one generic pipeline that is generically executable in a plurality of different continuous integration and delivery (CI/CD) environments, the creating comprising:
incorporating at least one stage script into the at least one generic pipeline, the at least one stage script defining a flow for the at least one generic pipeline and calling on utility libraries to perform their functions at appropriate points in the flow; and
provisioning the virtual container with features from at least a portion of at least one utility library, the features including instructions for at least one generic application task during at least one step in the flow of the at least one generic pipeline;
creating, by the processor, a separate pipeline definition for executing the generic pipeline within each of the plurality of different CI/CD environments, each pipeline definition indicating the CI/CD environment for which it is created and being configured to operate only in the CI/CD environment for which it is created, and each pipeline definition comprising a build script that, when executed in the CI/CD environment for which it is created, causes the CI/CD environment to execute the at least one generic pipeline; and
deploying, by the processor, at least one of the pipeline definitions along with the virtual container in the CI/CD environment for which the at least one of the pipeline definitions is created, thereby enabling execution of the at least one generic pipeline within the CI/CD environment for which the at least one of the pipeline definitions is created, wherein transitioning a pipeline from the CI/CD environment for which the at least one of the pipeline definitions is created to another CI/CD environment includes customizing only the build script for the other CI/CD environment.
2. The method of claim 1 , wherein the creating of the virtual container further comprises creating the at least one utility library and incorporating the at least one utility library into the at least one generic pipeline.
3. The method of claim 1 , further comprising creating, by the processor, the at least one stage script.
4. The method of claim 1 , wherein each separate pipeline definition comprises a build script for the CI/CD environment for which the separate pipeline definition is created, the build script being configured to cause the CI/CD environment to cause the at least one generic pipeline to execute within the virtual container.
5. The method of claim 4 , further comprising creating, by the processor, the build script.
6. The method of claim 1 , wherein:
at least one of the plurality of different CI/CD environments comprises a local development environment; and
the deploying comprises testing the at least one generic pipeline in the local development environment prior to deploying the at least one generic pipeline in at least one of the plurality of different CI/CD environments separate from the local development environment.
7. The method of claim 1 , wherein the at least one stage script is provisioned with additional features from outside the at least one utility library during at least one step in the flow of the at least one generic pipeline.
8. A generic pipeline development system comprising:
a processor; and
a non-transitory memory in communication with the processor, the memory comprising instructions that, when executed by the processor, cause the processor to perform processing comprising:
creating a virtual container including at least one generic pipeline that is generically executable in a plurality of different continuous integration and delivery (CI/CD) environments, the creating comprising:
incorporating at least one stage script into the at least one generic pipeline, the at least one stage script defining a flow for the at least one generic pipeline and calling on utility libraries to perform their functions at appropriate points in the flow; and
provisioning the virtual container with features from at least a portion of at least one utility library, the features including instructions for at least one generic application task during at least one step in the flow of the at least one generic pipeline;
creating a separate pipeline definition for executing the generic pipeline within each of the plurality of different CI/CD environments, each pipeline definition indicating the CI/CD environment for which it is created and being configured to operate only in the CI/CD environment for which it is created, and each pipeline definition comprising a build script that, when executed in the CI/CD environment for which it is created, causes the CI/CD environment to execute the at least one generic pipeline; and
deploying at least one of the pipeline definitions along with the virtual container in the CI/CD environment for which the at least one of the pipeline definitions is created, thereby enabling execution of the at least one generic pipeline within the CI/CD environment for which the at least one of the pipeline definitions is created, wherein transitioning a pipeline from the CI/CD environment for which the at least one of the pipeline definitions is created to another CI/CD environment includes customizing only the build script for the other CI/CD environment.
9. The system of claim 8 , wherein the creating of the virtual container further comprises creating the at least one utility library and incorporating the at least one utility library into the at least one generic pipeline.
10. The system of claim 8 , wherein the processing further comprises creating the at least one stage script.
11. The system of claim 8 , wherein each separate pipeline definition comprises a build script for the CI/CD environment for which the separate pipeline definition is created, the build script being configured to cause the CI/CD environment to cause the at least one generic pipeline to execute within the virtual container.
12. The system of claim 11 , wherein the processing further comprises creating the build script.
13. The system of claim 8 , wherein:
at least one of the plurality of different CI/CD environments comprises a local development environment; and
the deploying comprises testing the at least one generic pipeline in the local development environment prior to deploying the at least one generic pipeline in at least one of the plurality of different CI/CD environments separate from the local development environment.
14. The system of claim 8 , wherein the at least one stage script is provisioned with additional features from outside the at least one utility library during at least one step in the flow of the at least one generic pipeline.
15. A method of developing at least one generic pipeline, the method comprising:
creating, by a processor, a virtual container including at least one generic pipeline that is generically executable in a plurality of different continuous integration and delivery (CI/CD) environments, the creating comprising:
incorporating at least one stage script into the at least one generic pipeline, the at least one stage script defining a flow for the at least one generic pipeline and calling on utility libraries to perform their functions at appropriate points in the flow; and
provisioning the virtual container with features from at least a portion of at least one utility library, the features including instructions for at least one generic application task during at least one step in the flow of the at least one generic pipeline;
creating, by the processor, a separate pipeline definition for executing the generic pipeline within each of the plurality of different CI/CD environments, each pipeline definition indicating the CI/CD environment for which it is created and being configured to operate only in the CI/CD environment for which it is created, and each pipeline definition comprising a build script that, when executed in the CI/CD environment for which it is created, causes the CI/CD environment to execute the at least one generic pipeline; and
deploying, by the processor, at least one of the pipeline definitions along with the virtual container in a local development environment configured to simulate the CI/CD environment for which the at least one of the pipeline definitions is created, wherein transitioning a pipeline from the CI/CD environment for which the at least one of the pipeline definitions is created to another CI/CD environment includes customizing only the build script for the other CI/CD environment.
16. The method of claim 15 , wherein the creating of the virtual container further comprises creating the at least one utility library and incorporating the at least one utility library into the at least one generic pipeline.
17. The method of claim 15 , further comprising creating, by the processor, the at least one stage script.
18. The method of claim 15 , wherein each separate pipeline definition comprises a build script for the CI/CD environment for which the separate pipeline definition is created, the build script being configured to cause the CI/CD environment to cause the at least one generic pipeline to execute within the virtual container.
19. The method of claim 18 , further comprising creating, by the processor, the build script.
20. The method of claim 15 , wherein the at least one stage script is provisioned with additional features from outside the at least one utility library during at least one step in the flow of the at least one generic pipeline.