Continuous Integration and Continuous Delivery Pipeline for Low Code and No Code Application Platform

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.

2. 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.

3. 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.

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

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

6. 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.

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

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.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.

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.

16. 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.

17. 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.

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

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

20. 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.