# US 2025/0147745 A1 · Query-backed ci/cd pipeline modules and distribution method > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2025/0147745 A1 - Document ID: US20250147745A1 - Status: Published application - Kind: A1 - Application number: 18/936,794 - Filed: 2024-11-04 - Published: 2025-05-08 - Earliest claimed: 2023-11-06 - Assignees: Dagger, Inc. - Applicants: Dagger, Inc. - Inventors: Solomon Hykes; Erik Sipsma; Andrea Luzzardi; Sam Alba - Web page: https://patentgrep.com/patent/US20250147745A1 ## CPC - G06F 8/61: Installation - G06F 9/45508: {Runtime interpretation or emulation, e g. emulator loops, bytecode interpretation} - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract In one embodiment, using a script automation processor hosted using a virtual compute instance and a virtual storage instance associated with media storing sequences of instructions defining an API implementation of an API, a graph server, and programming language runtime interpreters, a method includes obtaining access to a user pipeline automation script comprising sequences of instructions specifying API calls to the API, creating and storing modules extending the API from the user pipeline automation script, wherein some of the modules are re-usable, creating and storing programmatic containers corresponding to the modules, creating and storing a directed acyclic graph (DAG) comprising nodes and edges corresponding to dependencies of the containers, interpreting each module using a particular programming language runtime interpreter among the programming language runtime interpreters, installing the modules in association with the API implementation. ## Claims ### Claim 1 A computer system comprising: a script automation processor; and a virtual compute instance and a virtual storage instance associated with one or more non-transitory computer-readable storage media storing one or more first sequences of instructions defining an API implementation of an API, a graph server, and one or more programming language runtime interpreters, and which, when executed using the virtual compute instance, cause the virtual compute instance to execute: obtaining access to a user pipeline automation script comprising one or more second sequences of instructions specifying one or more API calls to the API; executing the script automation processor; creating and storing one or more modules in one or more programming languages from the user pipeline automation script, the one or more modules extending the API, wherein one or more of the modules are re-usable; creating and storing one or more programmatic containers in memory of the script automation processor, the containers corresponding to the one or more modules; creating and storing a directed acyclic graph (DAG) in the memory of the script automation processor, the DAG comprising nodes and edges corresponding to dependencies of the containers; interpreting each of the one or more modules using a particular programming language runtime interpreter among the one or more programming language runtime interpreters; and installing the one or more modules in association with the API implementation. ### Claim 2 (depends on 1) The computer system of claim 1, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: generating a command line interface (CLI); receiving, via the CLI, an initiation command configured to create a first module; and creating and storing the first module. ### Claim 3 (depends on 2) The computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a function calling command configured to execute a function associated with the first module; and executing the function associated with the first module in a programmatic container of the one or more programmatic containers. ### Claim 4 (depends on 2) The computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a modification command configured to modify the first module; modifying the first module; and receiving, via the CLI, a synchronization command configured to reload the first module. ### Claim 5 (depends on 2) The computer system of claim 2, a function associated with the first module being configured to take and return data objects associated with a plurality of types. ### Claim 6 (depends on 2) The computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a module calling command configured to add a dependency of a second module to the first module; executing the first module; and during the execution of the first module, calling and executing the second module. ### Claim 7 (depends on 2) The computer system of claim 2, wherein the first module is stored in two or more repositories, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a function calling command specifying a first repository of the two or more repositories; consuming the first module from the first repository; and executing the first module. ### Claim 8 (depends on 2) The computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a module publishing command specifying a repository to publish the first module; and publishing the first module in the repository. ### Claim 9 (depends on 2) The computer system of claim 2, wherein a first function is associated with the first module, wherein the first function is configured to return custom objects defining one or more second functions. ### Claim 10 (depends on 9) The computer system of claim 9, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a function calling command configured to execute the first function; executing the first function; and during the execution of the first function, calling and executing the one or more second functions. ### Claim 11 (depends on 1) The computer system of claim 1, wherein at least a first function is associated with a first module of the one or more modules, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: executing the first function; and instantiating and returning one or more services from the first function. ### Claim 12 (depends on 11) The computer system of claim 11, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: creating and storing one or more programmatic service containers in memory of the script automation processor, the service containers corresponding to the one or more services. ### Claim 13 (depends on 12) The computer system of claim 12, wherein each of the service containers comprises a service hostname configured for querying the corresponding service container. ### Claim 14 (depends on 12) The computer system of claim 12, wherein each of the service containers comprises one or more ports configured to expose the corresponding service to a host. ### Claim 15 (depends on 14) The computer system of claim 14, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via one or more of the ports, a request to use the first service from a client on the host; and executing the first service. ### Claim 16 (depends on 12) The computer system of claim 12, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: binding a first service of the services executing in a first service container of the service container to a client container; and automatically starting the first service when the client container executes. ### Claim 17 (depends on 12) The computer system of claim 12, wherein a first service of the services executes on a host, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: binding a first container of the containers to the first service; executing the user pipeline automation script to automatically build, test, or deploy a user application in a cloud computing service; and during the executing of the user pipeline automation script, querying the first service by the first container. ### Claim 18 (depends on 12) The computer system of claim 12, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute creating and storing, in the DAG, nodes corresponding the services and edges corresponding to bindings associated with the services. ### Claim 19 (depends on 1) The computer system of claim 1, the script automation processor further comprising two or more programming language runtime interpreters, wherein each programming language runtime interpreter among the two or more programming language runtime interpreters is programmed to interpret a different programming language used in each of the one or more modules. ### Claim 20 (depends on 1) The computer system of claim 1, wherein the script automation processor further comprises the second sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: executing the user pipeline automation script to automatically build, test, or deploy a user application in a cloud computing service; and during the executing, based on the user pipeline automation script, invoking one or more of the one or more modules as part of automatically building, testing, or deploying the user application in the cloud computing service. ### Claim 21 (depends on 1) The computer system of claim 1, wherein the user pipeline automation script further comprises at least one reference to a software development kit (SDK), and wherein the script automation processor comprises an SDK interface responsive to function invocations via the at least one reference. ### Claim 22 A computer-implemented method comprising: using a script automation processor that is hosted using a virtual compute instance and a virtual storage instance associated with one or more non-transitory computer-readable storage media storing one or more first sequences of instructions defining an API implementation of an application programming interface (API), a graph server, and one or more programming language runtime interpreters, obtaining access to a user pipeline automation script comprising one or more second sequences of instructions specifying one or more API calls to the API; using the script automation processor, creating and storing one or more modules in one or more programming languages from the user pipeline automation script, the one or more modules extending the API, wherein one or more of the modules are re-usable; using the script automation processor, creating and storing one or more programmatic containers in memory of the script automation processor, the containers corresponding to the one or more modules; using the script automation processor, creating and storing a directed acyclic graph (DAG) in the memory of the script automation processor, the DAG comprising nodes and edges corresponding to dependencies of the containers; using the script automation processor, interpreting each of the one or more modules using a particular programming language runtime interpreter among the one or more programming language runtime interpreters; and using the script automation processor, installing the one or more modules in association with the API implementation. ### Claim 23 One or more non-transitory computer-readable storage media storing one or more sequences of instructions which, when executed using one or more processors, cause the one or more processors to: using a script automation processor that is hosted using a virtual compute instance and a virtual storage instance associated with one or more non-transitory computer-readable storage media storing one or more first sequences of instructions defining an API implementation of an application programming interface (API), a graph server, and one or more programming language runtime interpreters, obtaining access to a user pipeline automation script comprising one or more second sequences of instructions specifying one or more API calls to the API; using the script automation processor, creating and storing one or more modules in one or more programming languages from the user pipeline automation script, the one or more modules extending the API, wherein one or more of the modules are re-usable; using the script automation processor, creating and storing one or more programmatic containers in memory of the script automation processor, the containers corresponding to the one or more modules; using the script automation processor, creating and storing a directed acyclic graph (DAG) in the memory of the script automation processor, the DAG comprising nodes and edges corresponding to dependencies of the containers; using the script automation processor, interpreting each of the one or more modules using a particular programming language runtime interpreter among the one or more programming language runtime interpreters; and using the script automation processor, installing the one or more modules in association with the API implementation.