Announcement: Continuous Integration for Fiori on ABAP Front-End Server

[krzys]

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 SAPUI5/Fiori development on ABAP Front-End server".

In this scenario we describe what it takes to build Fiori applications within an automated CI pipeline using Jenkins and open source tools. An important part of this pipeline is the deployment to an ABAP front-end server: We explain how a CI pipeline can be coupled to traditional ABAP transport mechanisms. This allows you to combine the more development centric qualities of CI with the your ABAP life cycle management tooling.

If you're new to Continuous Integration, don't despair! For the CI and CD beginner we also explain the basics of these processes, important practices, and we're taking time to describe the tools that are necessary to implement it. Check out this overview of all the topics covered.

We hope you enjoy it, let us know what you think!

[Former Member]

Thank you very much for your interest. I try to give a short answer:

1. Yes, we plan to cover this topic in the future, especially for the combination Fiori or SAPUI5 together with backend services, there will be a solution. On which platform do you plan to run your OData service? On SAP Cloud Platform?

2. Any solution that is able to instrument the native RFC library would be possible from a CI process. For Fiori that is JavaScript, the node-rfc module was appropriate, but SAP Java Connector (if you prefer e.g. Maven as build tool) https://help.sap.com/saphelp_nwpi711/helpdata/en/48/70792c872c1b5ae10000000a42189c/content.htm should work as well, though I personally did not work with it so far.

3. We have left this topic open so far since, first, there are many possible implementations and customers have usually different preferences which one to choose. and secondly, we concentrated in our description so far on the core CI process.

I hope this could help you a little bit.

[former_member186450]

This is great. We are starting our journey to implement this in the development life-cycle for SAPUI5.

a couple of questions I have so far.

1) is there any plan to expand the scope of the CI/CD process to cover CDS views and OData services development?

2) is the node-rfc the only alternative to enable the CD process from the CD pipeline to ABAP?

3) any plans to include code quality checks in SONARQUBE for SAPUI5?