Another piece of the puzzle falls into place: SAP Continuous Integration and Delivery now supports event notifications using SAP Alert Notification Service.
Being developers ourselves, we understand your development needs. Notifying the team about a...
SAP Continuous Integration and Delivery offers ready-to-use pipelines, specifically for SAP development scenarios. One of those scenarios is developing CAP-based applications and extensions on SAP BTP. In the last couple of months we spent some time ...
Co-author sarah_n#overview
Project “Piper” is an open source continuous delivery (CD) offering by SAP, which can be used as a shared library for the automation server Jenkins. The library contains the implementation of steps, scenarios, and utilitie...
At the end of exciting year with lots of additions to our Continuous Integration Best Practices Guide, we were very proud to show off our latest addition to our CI/CD offering at TechEd in Barcelona:
Jenkins Pipelines for SAPUI5 and Fiori Development...
A mature development process, such as Continuous Integration (CI), is commonly regarded as essential for fast and reliable application development for the cloud. In our series of CI best practices for SAP customers, we just added "best practices for ...
Good news everyone: This is possible. the feature has been implemented.Here's the documentation:https://help.sap.com/docs/continuous-integration-and-delivery/sap-continuous-integration-and-delivery/administering-jobs?language=en-USAnd here's a blog e...
Hi there,your assumption is correct, the "Cloud Foundry Environment" pipeline is the one for you. We have recently updated and renamed the pipelines -- we'll update the tutorial as soon as possible.Thanks for reaching out!Christoph
Hello,please open a support ticket (component BC-CP-CF-CICD), attach the full build log and we'll have a look at it. From the screenshots it's hard to tell what's going wrong.Thanks!Christoph
As it is best practice to not directly push code onto the main Branch, [...] Just to be safe.Agreed. To solve that problem at the core, protect your main branch. I'd like to only build on a successful merge, and thus exclude any accidental non-merge ...