Closed Nico31300 closed 4 years ago
Hello,
I finally found my solution. The step transportRequestUploadFile is the good one but there is a "secret" parameter. Never mentioned in documentation applicationId:
steps:
transportRequestUploadFile:
abapPackage: ''
applicationDescription: ''
applicationId: 'FIORINW'
With this parameter you need to send the result of your build zipped to the server.
Hello,
Context
I try to put in place a CI/CD pipeline for SAPUI5 application for my company. The development phase is done in WebIDE (NEO environment) Code is saved in a private Github server (on the LAN) SAPUI5 application is pushed to an on premise server. Transports are managed by CharRM.
Goal
Project Piper implementation
Since few weeks I'm practicing on project piper (you can find some issues posted by me ^^ ), I finally managed to get step transportRequestUploadFile to work but i'm note sure it's the good approach. Because a mtar file is saved on the SAPUI5 server (on the transport request) but the BSP application is not deployed on the server. I don't know what to do with this archive in the transport request.
When I read the documentation of scenario Build an SAP Fiori Application and Attach It to a Transport Request on an ABAP System with Jenkins we can see
Based on that i assumed that the BSP application will be pushed on my SAP ABAP system, but it's not the case.
Help
Could you say me if i can reach my goal using project piper ? Which step i need to implement if transportRequestUploadFile is not the good one ? I have seen an issue where it's mentioned to use RFC method instead of OData. Or maybe my configuration is not good ?
Annexes
Github repo : https://github.com/Nico31300/devops