Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the SAP Continuous Integration and Delivery service #17

Merged
merged 2 commits into from
Feb 14, 2023
Merged

Add the SAP Continuous Integration and Delivery service #17

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
15ea5c6
Add the SAP Continuous Integration and Delivery service
LindaSieb Feb 8, 2023
77d78a6
Update deploying-applications-866ab13.md
annawenger20 Feb 14, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/deploy-and-deliver/deploying-applications-866ab13.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ There are two options for deploying MTAs: Manually or managed.

- **Manually:** You can archive all components of your application into one package that includes the deployment descriptor. You can then manually trigger the deployment of the solution using the SAP BTP cockpit or the Console Client. The actual deployment of the MTA files is then performed automatically by the SAP BTP deployment infrastructure, considering all interdependencies specified in the MTA deployment descriptor that is part of the MTA archive. By assigning roles and encapsulating the Console Client in a script, you can achieve a somewhat controlled release mechanism.

- **Managed:** If you prefer a managed approach, you can deploy MTAs as part of a CI/CD approach or implement transport or change management processes for your SAP BTP apps, using enhanced Change and Transport \(CTS+\) for example. For more information, see [Transporting Multitarget Applications with CTS+](https://help.sap.com/viewer/ea72206b834e4ace9cd834feed6c0e09/Cloud/en-US/f598f69a9be347029b7e5e7205fc7d1f.html "You can enable transport of SAP BTP applications and application content that is available as Multitarget Applications (MTA) using the Enhanced Change and Transport System (CTS+).") :arrow_upper_right:.
- **Managed:** If you prefer a managed approach, you can deploy MTAs as part of a CI/CD approach. See [SAP Continuous Integration and Delivery service](https://help.sap.com/docs/CICD_OVERVIEW) for more information. Or you can implement transport or change management processes for your SAP BTP apps, using enhanced Change and Transport \(CTS+\) for example. For more information, see [Transporting Multitarget Applications in Cloud Foundry using CTS+](https://help.sap.com/docs/btp/sap-business-technology-platform/transporting-multitarget-applications-in-cloud-foundry-using-cts).

**Related Information**

Expand Down