Using one Power Pipeline for multiple projects

[PowerBi-Rick]

I am an ISV and have a multi-layered set of Model Driven Apps. I am trying to use Power Pipelines for ALM. I have created an Incident Tracking App and a Program Tracking App. Both of these Apps use a core set of Lookup tables. Customers have the ability to purchase the Incident App, the Program App or both. For development I have three different environments. 

Environment 1 Solution 1 - Lookup Tables used in both Incident App and Program App

Environment 2 Solution 2 - Incident App

Environment 3 Solution 3 - Program App

For the Incident App I pull in a managed version of the Lookup Tables. I do the same for the Program App.

In my Pipeline Host Environment 1 I added the following Environments

Lookup Dev

Lookup Test

Incidents Dev

Program Dev

I am able to create pipelines for

Lookup Dev --> Lookup Test

Lookup Dev --> Incidents Test

Lookup Dev --> Program Test

When I try to create a target environment for Incidents (Incidents Test) to be able to deploy from Incidents Dev

I get a Business Process error that the Environment Id for Incidents Test already exists (since it is being referenced for Lookup Dev --> Incidents Test). 

My hope was I could do everything in parallel within the same Hosting Environment, but that won't work.

If I create a two more Host Environments, one for Incidents and one for Program can I first deploy the Lookups from Host Environment 1 (since the Lookups Solution has to be installed first anyway due to dependencies) and then run these pipelines to install the solutions on top of the already installed Lookups?

Host Environment 2: Incidents Dev --> Incidents Test

Host Environment 3: Program Dev --> Program Test

[parvezghumra]

@PowerBi-Rick I haven't done much with the in platform pipeline, but it feels like your requirements are probably a bit too advanced and you might benefit from considering Azure DevOps pipelines or GitHub Actions for your ALM strategy

[PowerBi-Rick]

Thanks for the input. I am still hoping to simplify things and use Power Pipelines. 

Anyone from Microsoft, is it possible that Source A (Environment ID XXXXXXXX) could deploy to Target Source C (Environment ID ZZZZZZZZ) and Source B (Environment ID YYYYYYYY) could also deploy to Target Source C (Environment ID ZZZZZZZZ)?

I am wondering if the underlying Model Driven App for Power Pipelines is using a Business Rule to prevent the same Target ID from being using as a target in more than one pipeline or if that is done in code. If it is a Business Rule, could the rule permit the condition I describe above as long as Source A and Source B and NOT coming from the same Environment ID even though they are both pushing to Source C?

This would allow for creating multi-layered solutions more easily.