Change Default mta.yaml filepath in BTP CICD pipeline config.yaml

[hatrigt]

I have a full stack multi-tenant project. This repository has two MTA's. One is for the CAP related artifacts which is in the root directory. The other is inside the app folder which holds the artifacts related to the frontend(UI5). 

Now I need to setup my pipeline in BTP CICD. I added the github repository and tried to create a job. 
Herein I understood, if I select buildtool as mta, it searches for mta.yaml file in the root directory of repository. 
The thing is I need to setup two jobs one should pick mta in root directory and deploy in provider subaccount and other should pick mta from app folder and deploy it in subscriber subaccount. 

Is there any other option which we can set in config.yaml file inside .pipeline folder which will override the default mta.yaml filepath or atleast set the mta file name like mta-ui.yaml ??


@Nikitha09 

or is there any other way to achieve this?

SAP Continuous Integration and Delivery 

[gregorw]

Can you explain us the reason why you split the CAP Backend and the UI5 Frontend in two different MTAs?

[hatrigt]

Hi @gregorw ,

We are adhering to the following strategy:

Provider Subaccount - CAP Apps will be deployed.
Consumer Subaccounts - UI5 Apps will be deployed.

In this scenario, we have multiple consumer subaccounts where I need to deploy the UI5 Apps on each, utilizing the MTA defined for the UI5 application.

We will be using single repository for both backend and frontend. 

[Nikitha09]

Hi @hatrigt,

Sorry for the late update. In general, it is possible to influence the path to the mta.yaml file but then you need to use the configuration mode as the source repository instead of the Job editor. In that way, you can define 2 jobs, one pointing to mta.yaml on root (by default ./)and another one pointing to mta.yaml file in sub folder with the following configuration in .pipeline/config.yaml file.

steps:
  mtaBuild:
    source: <path_to_the folder_containing_mta.yaml>

I hope this answers your questions. In case of any further questions, please get back to us.

Thanks and Regards,

Nikitha 

[sreehari_vpillai]

@Nikitha09 we managed it with a technical branch and a git workflow.