Discussion
Pegasystems Inc.
US
Last activity: 29 Jul 2022 4:57 EDT
Deployment Manager pain points
Deployment Manager community,
In another thread I had asked for your succes stories. Now I'd like to give an oportunity to tell us about things that could be better. Please share examples of tasks you've wanted to complete using Deployment Manager which were overly challenging or just not possible. Some requests are likely on our roadmap and we can set expectations of when we expect them to be addressed, while others we may not have been aware of.
This is not intended as a place to report feature bugs, those should go through the normal support channels.
-Ryan
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
ES
Hi !!,
What do you think about these features?
- Being able to run static assembler from CI/CD pipeline, at least on production environment
- Sometimes our clients works with third orchestration server, like jenkins or Azure DevOps. New DM APIs are really usefull to integrate these third tools with Pega, being able to run a CI/CD pipleine throuth the Rest API. I missed being able to configure in any way a callback to the third orchestration server whith CI/CD DM result, either is a success or not.
- Being able to configure approval from third tools, eg. calling an external web service and processing the response as an async callback.
Thanks!!
Pegasystems Inc.
US
Hi elvad,
- What is the use case for #1, reducing FUA? This is not something we're considering at this time.
- As far as callbacks when a DM CI/CD task or pipeline has completed, we are considering a message bus which supports publish and subscribe to DM topics, but that's further in the future. In the interim you could solve this by polling the DM.
- The plan is to continue to extend the API's to support every action which is possible via the UI, which would include automated approval. You'll see this support grow over the next 6 months to a year.
Thanks for the feedback,
-Ryan
Areteans
AU
Hi Ryan,
Allowing the Pipeline to run the Multiple Deployments i.e. Case Wise processing of the deployments.
Currently, the Deployment Manager does not support the Parallel deployments due to the Single thread approach followed. Will be very helpful if we can get a case type kind of processing on top of the deployment manager which will ease the approval process.
Thanks.
TD
CA
@AbdulQaderM completely agree! Not having the ability to run multiple deployments on the same pipeline in parallel means more manual work during releases. This will be a great feature if enabled in future versions of the product.
Accenture
AU
Here's some of the pain points / ideas
- A release can have several deployments , did not come across a way of grouping multiple deployments in a Release
- Ability to invoke REST services from the pipeline , this will open up a whole new world of integrations to 3rd party tools say for infra provisioning
- Ability to add group notifications and and work queues for manual steps in pipeline
- +1 for Abdul's point
TD
CA
I wanted to add similar feedbacks to this thread..
Pegasystems Inc.
US
Customer has more than 5 environments and would like to have the ability to customize the name of each of the stages in the pipeline. For example, pipeline DevSITUATPRE would have stage names of Dev, Sit, UAT and Pre whereas another pipeline for DevSITUATPPE would have Dev, Sit, UAT and PPE
W & W Informatik GmbH
DE
Hey Ryan @feenr,
I am bumping an older discussion here and I hope that's OK.
We run about 40 Pega systems in a "private cloud" on premise (incl. Dev, Test, Staging) and use PDM for all deployments. We have a huge number of pipelines.
Features we would like:
Hey Ryan @feenr,
I am bumping an older discussion here and I hope that's OK.
We run about 40 Pega systems in a "private cloud" on premise (incl. Dev, Test, Staging) and use PDM for all deployments. We have a huge number of pipelines.
Features we would like:
- Trigger static assembler after deploying an app, to reduce FUA. This is needed in many of our apps and is currently a taks that our ops-people need to do manually after an otheriwse automatic deployment.
- Deploy to multiple production systems in parallel; that would be helpful for shared components / enterprise layer which we need to deploy to multiple environments.
- Dependency management, especially transitive dependencies (if A needs B and B needs C, A+B+C will be deployed). Also, we would love if the dependencies could be defined at design time in Dev Studio / App Studio (maybe on Product level or from a centralized catalogue?) and be imported to PDM.
- Improved SSO and support for user roles; we would like to configure privileges and visible pipelines based on user role from IDP; maybe using Decision table or similar config.
- Custom checks as part of pipeline; e.g. if certain data instances or rules are included in a product, stop pipeline and ask for review. Would be great if that was an extension point that could be adjusted as needed (thinking when rules, decision table / tree or activity here).
Biggest pain point is currently performance and resource consumption, especially with large RAP and parallel deployments; but supposedly that should be better with latest version - we're in the process of upgrading to 5.5.3.
Thanks and kind regards from Germany Malte