Pipeline Environment as Target and Development

Like (1) Share

Report

Posted on 12 Feb 2025 14:57:25 by EV-13121856-0

Hi,

I have set up four environments: CrossData (for organizational tables with unmanaged solutions), Dev (for application development with unmanaged solutions and managed solutions from CrossData), Test (for testing all managed solutions), and Prod (for operating all managed solutions).

I successfully built a pipeline to deploy from CrossData to Dev, leveraging solution layering since the base layer of organizational tables is stored in the CrossData environment. This setup works fine.

Now, I want to create a pipeline to deploy from Dev to Test. However, I cannot use the Dev environment because it is already a target type in the previous pipeline. I aim to deploy both the CrossData managed solution and the APP unmanaged solution from Dev to Test, but I am unsure how to set this up.

Can you provide any ideas, guidance, or advice? Thanks.

Categories:

Management

All responses (1)

Answers (0)

Suggested answer

AlbertoCastro 1,184 Most Valuable Professional on 12 Feb 2025 at 15:39:22

Like (0)

Report

Pipeline Environment as Target and Development

Hi,
yes, this a expected behaviour of the product. An environment only can be Developmentor or Target.

A Development environment can be used like source of different pipelines

A Target environemt can be used like destiny of different pipelines.

But one environment can't be development env for one pipeline and targer for other.

---------------------------
If the solution works, please kindly ✅ check the box "Does this answer your question?" on the bottom left! This will help others in finding the solution more expediently 😄 Also, a Like would be a great compliment!