Showing results for 
Search instead for 
Did you mean: 

Fiori Source Code assets versioning and protection

0 Kudos

I worked full time in a ReactJS Project where 4 developers were involved.

We did everything in a github private repository.

Leader did the Ci Cd and deployed.

How is this done in SAP Fiori/SAP-UI5?

I have used deploy in a test server and seen "objects" go to SAP BSP application object. Fiori/UI5 app seem well integrated with CTS but what about the source code in snippets that remain in DEVSPACE for BAS or PC in case of VSCODE. Or the sequence of "generation" that yeoman has done.

How are source code assets protected and kept centrally?

How is source code versioned esp when multiple deployers working on same Fiori App.

As I have experience in ABAP I look for the same "comfort" of integration with CTS for source and objects generated js xml yaml etc.

Generated code esp for fiori elements means all js files etc. may not reverse engineer the sequemce of screens the developer have have navigated. This lack of production developer sync may be a problem?
ABAP Objects and SmartForms stay inside the server in on-premise.
But in BTP what happens?
What if a developer quits and another assigned maintenance task of Fiori elements?

I suppose organization has to depend on any documentation programmer has done?

Searched a lot but could not find any clear document covering the above questions/concerns.
Please help clarify my doubts.


Accepted Solutions (0)

Answers (1)

Answers (1)

Active Contributor
0 Kudos

for version management, ui5 has no difference from what you do with react project

traditional abap object version management is not that "applicable" to ui5, abap server TR is just used to transport ui5.

0 Kudos

Thanks! Yor answer is good.
Let me wait some time to see if at all other opinions come.
I had requested a ref to a comprehensive document covering the above questions/concerns.

Some CIOs may not be comfortable of external github in landscape.
Fiori-freestyle and Fiori-elements both introduce risks when deveoper quits organization.
In traditional ABAP etc central dvelopment too developers and Functional Consultants wrote some external change history docs so that a new joinee can trace changes from a human perspective.