# US 2024/0403035 A1 · Continuous integration and continuous delivery pipeline for low code and no code application platform

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0403035 A1
- Document ID: US20240403035A1
- Status: Published application
- Kind: A1
- Application number: 18/328,001
- Filed: 2023-06-02
- Published: 2024-12-05
- Earliest claimed: 2023-06-02
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Jian Li; Yan Zang; Sheng Yao; Qiu Shi Wang
- Web page: https://patentgrep.com/patent/US20240403035A1

## CPC

- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 8/34: Graphical or visual programming
- G06F 8/60: Software deployment
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, systems, and computer-readable storage media for receiving, through a set of user interfaces (UIs), user input including job configuration information and deployment information for an application, providing a CI/CD job for the application with a CI/CD service using the job configuration information and the deployment information, and triggering, in response to a commit of changes to the application in a repository, automated build of the application, and in response, automatically: generating a development descriptor file at least partially based on the user input, providing an archive file including the development descriptor file, and processing, by the CI/CD job executed by the CI/CD service, the archive file to deploy the application within the target environment.

## Claims

### Claim 1

A computer-implemented method for low-code/no-code (LCNC) provisioning of continuous integration and continuous delivery (CI/CD) pipelines for deployment of an application to cloud-based environments, the method being executed by one or more processors and comprising:
receiving, through a set of user interfaces (UIs), user input comprising job configuration information and deployment information for an application;
providing a CI/CD job for the application with a CI/CD service using the job configuration information and the deployment information; and
triggering, in response to a commit of changes to the application in a repository, automated build of the application, and in response, automatically:
generating a development descriptor file at least partially based on the user input,
providing an archive file comprising the development descriptor file, and
processing, by the CI/CD job executed by the CI/CD service, the archive file to deploy the application within the target environment.

### Claim 2 (depends on 1)

The method of claim 1, further comprising providing a webhook between the repository and the CI/CD service, the webhook providing a webhook push event sent to the CI/CD service to trigger the automated build of the application.

### Claim 3 (depends on 1)

The method of claim 1, wherein the deployment information comprises an application programming interface (API) endpoint, an organization name, a space name, and credentials for accessing an application project of the application within the repository.

### Claim 4 (depends on 1)

The method of claim 1, further comprising storing application artifacts of the application as an application project within the repository.

### Claim 5 (depends on 1)

The method of claim 1, wherein the set of UIs is provided by a CI/CD guided development module of an application development platform.

### Claim 6 (depends on 1)

The method of claim 1, wherein the development descriptor file is a manifest file comprising identification of one or more backend services used to execute CI/CD functionality, dependencies, and details of a process for build and deployment of the application.

### Claim 7 (depends on 1)

The method of claim 1, wherein the application is a multi-target application (MTA) that can be deployed to multiple, disparate target environments.

### Claim 8

A non-transitory computer-readable storage medium coupled to one or more processors and having instructions stored thereon which, when executed by the one or more processors, cause the one or more processors to perform operations for low-code/no-code (LCNC) provisioning of continuous integration and continuous delivery (CI/CD) pipelines for deployment of applications to cloud-based environments, the operations comprising:
receiving, through a set of user interfaces (UIs), user input comprising job configuration information and deployment information for an application;
providing a CI/CD job for the application with a CI/CD service using the job configuration information and the deployment information; and
triggering, in response to a commit of changes to the application in a repository, automated build of the application, and in response, automatically:
generating a development descriptor file at least partially based on the user input,
providing an archive file comprising the development descriptor file, and
processing, by the CI/CD job executed by the CI/CD service, the archive file to deploy the application within the target environment.

### Claim 9 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein operations further comprise providing a webhook between the repository and the CI/CD service, the webhook providing a webhook push event sent to the CI/CD service to trigger the automated build of the application.

### Claim 10 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the deployment information comprises an application programming interface (API) endpoint, an organization name, a space name, and credentials for accessing an application project of the application within the repository.

### Claim 11 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein operations further comprise storing application artifacts of the application as an application project within the repository.

### Claim 12 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the set of UIs is provided by a CI/CD guided development module of an application development platform.

### Claim 13 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the development descriptor file is a manifest file comprising identification of one or more backend services used to execute CI/CD functionality, dependencies, and details of a process for build and deployment of the application.

### Claim 14 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, wherein the application is a multi-target application (MTA) that can be deployed to multiple, disparate target environments.

### Claim 15

A system, comprising:
a computing device; and
a computer-readable storage device coupled to the computing device and having instructions stored thereon which, when executed by the computing device, cause the computing device to perform operations for low-code/no-code (LCNC) provisioning of continuous integration and continuous delivery (CI/CD) pipelines for deployment of applications to cloud-based environments, the operations comprising:
receiving, through a set of user interfaces (UIs), user input comprising job configuration information and deployment information for an application;
providing a CI/CD job for the application with a CI/CD service using the job configuration information and the deployment information; and
triggering, in response to a commit of changes to the application in a repository, automated build of the application, and in response, automatically:
generating a development descriptor file at least partially based on the user input,
providing an archive file comprising the development descriptor file, and
processing, by the CI/CD job executed by the CI/CD service, the archive file to deploy the application within the target environment.

### Claim 16 (depends on 15)

The system of claim 15, wherein operations further comprise providing a webhook between the repository and the CI/CD service, the webhook providing a webhook push event sent to the CI/CD service to trigger the automated build of the application.

### Claim 17 (depends on 15)

The system of claim 15, wherein the deployment information comprises an application programming interface (API) endpoint, an organization name, a space name, and credentials for accessing an application project of the application within the repository.

### Claim 18 (depends on 15)

The system of claim 15, wherein operations further comprise storing application artifacts of the application as an application project within the repository.

### Claim 19 (depends on 15)

The system of claim 15, wherein the set of UIs is provided by a CI/CD guided development module of an application development platform.

### Claim 20 (depends on 15)

The system of claim 15, wherein the development descriptor file is a manifest file comprising identification of one or more backend services used to execute CI/CD functionality, dependencies, and details of a process for build and deployment of the application.
