We can extend environments in pipeline by adding additional environment/stages in CD pipeline case type,however there is roadblock for this to happen because of hard coding of environment details instead of taking stage names dynamically.
Any reason for restricting pipeline to be used for only 4 environments?
Why stage names were hard coded in pzEditStages?
Yes, we can create another pipelines if we have multiple environments and run manually, is there a provision to call another pipeline automatically from previous executed pipeline?
We will formally release an ability to add multiple stages in a pipeline in next few months, and will recommend you to not tweak the current underlying infrastructure (case types). The system may not behave predictably.
Discussions with our customers suggested that 4 staged lifecycle is typically good enough to perform various tests and generate adequate confidence before deploying to production.
Can you share your application lifecycle with us. How many stages do you have in your lifecycle and what forms of testing are you doing in each stage ?
You may be able to trigger a pipeline from an existing pipeline using our extensible task infrastructure that we will release to our customers in the next few weeks. It will allow you to create custom tasks to suite your specific DevOps needs.
In the meanwhile, do you mind elaborating your use case slightly more ?
Please feel free to reach to out me at by sending me a private message on my Pega Profile here, and we can discuss this further.
Posted: 4 years ago
Posted: 11 Oct 2018 9:52 EDT
Uday Sandeep Sane (Uday Sandeep Sane)
System Engineer III