Systems and methods for building generic CI/CD pipelines

A non-transitory computer-readable medium comprising instructions that, when executed by a processor, cause the processor to deploy at least one application, the instructions comprising:

• application instructions 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, the at least one program including:
• at least one stage script defining a flow for the at least one program;
• and
• at least one utility library, the at least one utility library including instructions for at least one generic application task, wherein the at least one stage script ingests at least a portion of the at least one utility library during at least one step in the flow of the at least one program and ingests additional code outside the at least one utility library during at least one step in the flow of the at least one program;
• and
• a plurality of separate pipeline definition instructions from a generic pipeline definition for 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 being configured to cause the CI/CD environment for which it is created to execute the at least one program, 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 a generic build script for the other CI/CD environment.

An application development device 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 program that is generically executable in a plurality of different continuous integration and delivery (CI/CD) environments, the at least one program including:
• at least one stage script defining a flow for the at least one program;
• and
• at least one utility library, the at least one utility library including instructions for at least one generic application task, wherein the at least one stage script ingests at least a portion of the at least one utility library during at least one step in the flow of the at least one program and ingests additional code outside the at least one utility library during at least one step in the flow of the at least one program;
• creating a separate pipeline definition from a generic pipeline definition for 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 being configured to cause the CI/CD environment for which it is created to execute the at least one program, wherein at least one of the plurality of different CI/CD environments comprises a local development environment, and 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 a generic build script for the other CI/CD environment;
• and
• operating the local development environment, the operating comprising testing the at least one program in the local development environment prior to deploying the at least one program in at least one of the plurality of different CI/CD environments separate from the local development environment.