Question
LTI
IN
Last activity: 14 Jul 2020 3:05 EDT
Rename stages in pega deployment manager
we have below requirements for deployment manager.
1) We need to deploy production products only on weekend is there a schedule option or do we need to use jenkins?
2) We need to rename stages to different name like QA to PPT
3) Adding more stages as currently only 4 stages are supported.
4) deploying only selected packages to production rather than one pipeline for each?
Regards,
Sajjad
***Edited by Moderator Kayla to update Content Type from Discussion to Question***
Pegasystems Inc.
IN
The first two requirements are on our road map; ability to schedule deployments during a maintenance window, ability to rename stages.
For the 3rd one here is a way you can achieve that: https://collaborate.pega.com/discussion/how-can-i-support-more-four-stages-pipeline. And improving this experience and making it more intuitive is also on our road map.
Can you shed more light on the 4th requirement? Are you asking for the ability to deploy to production only selected deployments? You can do that by using the deploy existing artifact feature.
LTI
IN
Hi Anil,
Please find more details on the same
3) Adding more stages as currently only 4 stages are supported.
<sajjad> We have 6 environments to support. From the article we can reduce but is there a way to increase number of environments say 6 envs?
4) deploying only selected packages to production rather than one pipeline for each?
<Sajjad> Using the deploy existing artifact feature we can select only 1 artifact we need ability to select multiple artifacts.
Regards,
Sajjad
Pegasystems Inc.
IN
For 3) As of now only 4 stages are supported in a pipeline, but giving the flexibility to add more stages is on the roadmap. So for 6 environments, creating multiple pipelines and triggering one from another is the only option.
For 4) If you package the entire application, you will only need to do deploy existing artifact with only 1 artifact. Deployment Manager works with the premise that you are packaging the entire application. Here is the recommendation on the same: https://collaborate.pega.com/discussion/how-should-my-application-product-rule-be-configured . If you absolutely need to deploy multiple artifacts then triggering the pipeline multiple times once with each artifact is the option.