Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
1,048
In this blog post I would like to give you some more details on the new features we have just released in SAP Continuous Integration and Delivery.

New Acceptance Stage for SAP Cloud Application Programming Model and SAP Fiori Pipelines


You can now configure an additional Acceptance Stage to your SAP Cloud Application Programming Model or SAP Fiori Job. Of course, this is also possible for already existing jobs - just edit your configuration and explore the new stage!

This new acceptance stage gives you the possibility to ensure any new functionality is tested end-to-end and there is no regression in existing functionality before deploying the application to your productive landscape.

For SAP Cloud Application Programming Model or SAP Fiori in the Cloud Foundry Environment you can now configure an additional deployment to a Cloud Foundry test space and run your automated tests, based on the UIVeri5 Framework against this instance of the application.


 

For SAP Fiori in the Neo Environment the configuration looks similar - the only difference are the specific settings for the deployment to a Neo Test Subaccount:



 

If you are new to UIVeri5, check this UIVeri5 page.

Further details for the configuration can be found on our updated documentation for the corresponding pipeline.

 

Manage Timed Triggers for Your Jobs


You can now not only trigger your job manually in SAP Continuous Integration and Delivery or automate your job triggering via WebHooks, but you can also configure your job to be automatically triggered according to schedules.

In the detail view of your job in SAP Continuous Integration and Delivery, navigate to the Timed Triggers tab and choose + (Create timed trigger)


 

In the Create Timed Trigger pop-up, enter the branch on which the build is executed and a cron schedule expression to define the recurrence condition of the build.


 

In the drop down, you can find some examples for cron patterns:


More examples and detailed information can be found in our documentation for this feature: Manage Timed Triggers for Jobs

 

Hope you have found this information useful! Additionally, we have updated our planned new features for Q4 2021 – check what we have already in our roadmap and if you miss something, post your feature request in SAP Continuous Influence or leave us a comment.