Hello teamI have a question about OutSystems LifeTime.
Suppose we have multiple environment sets under a single LifeTime, such as:
In this case, is it possible to manage different deployment pipelines per application, such as:
In other words, I would like to know whether it is possible to operate separate deployment environment flows for each application within a single LifeTime. Regards,
Hello Kazuna,
You need to create 2 deployment plans one for DEV to TEST
and another for TEST to PROD
Thanks,
Sudip
Hello,
Yes you can, consider the lifetime as the central operating unit that controls the 3 environments.
Also inspect these documentations:
@Sudip Pal @Sherif El-Habibi
Thank you for your response. I understand the deployment plans.
Additionally, I would like to ask about another scenario. Instead of having separate applications for A and B, we are considering using a single shared application in a common development environment and deploying it to two independent environment sets (each consisting of a testing environment and a production environment). For example, the setup would be as follows: ・Shared development environment (Dev) ・Environment set 1 (Test / Prod) ・Environment set 2 (Test / Prod) In this kind of setup, would it still be possible to manage deployments using a deployment plan? If there are any other recommended approaches, I would also appreciate your advice.Regards,
Hi @Kazuna Fujimori
OutSystems LifeTime is primarily designed around a linear deployment pipeline:
Dev → Test → Prod
When you introduce:
→ Test1 → Prod1
Dev →
→ Test2 → Prod2
you are essentially creating branching deployment paths. This is supported. For more details you can have a look on below post. Two ways deployment set up in Lifetime | OutSystems