Question
Anamata
NL
Last activity: 16 Feb 2023 1:48 EST
Dependency selection issue in Deployment Manager
I'm currently setting up a deployment pipeline in Deployment Manager 5.5.4 and i'm struggling with configuring the dependency settings.
I have the option to select my built-on application in the "Application name" dropdown. In addition I can select the the application version in the "Application version" dropdown. But after selecting these to the dropdowns "Pipeline" and "Deployment" remain empty.
If I ONLY select my built-on application in "Application name" and NOT the "Application version", I do have the option to select a "Pipeline" and a "Deployment".
However, all 4 fields are mandatory. What am I missing here?
Edit: Small addition. I believe it seems to have something to do with how the repository type is passed to D_ArchiveListInt. If I revert back to the previous version of the GetArchiveListInt activity, then I can select all 4 fields. Bug?
***Edited by Moderator Marije to add Capability tags***
Pegasystems Inc.
IN
@Michel KraaijYou can configure dependency on an application with given version only if the application with the given version has a pipeline and an active deployment (that is published to production).
Let me know if that helps.
More info - https://docs.pega.com/bundle/deployment-manager/page/deployment-manager/dm/configure-app-dependencies_1.html
Updated: 16 Feb 2023 1:48 EST
Anamata
NL
@nayamHmm, okay. I will try and play with it a little more. But why only packages that have a published to production state? That doesn't make sense to me. Dependencies are also important for deployments that haven't reached the production state yet, like deployments to a test environment.