Problem setting devops Pipeline CI CD
Hello :
I tried to follow the setup as described in this page for Pega 7.31 Platform ---> https://pdn.pega.com/deployment-manager-version-010101-and-020101/deployment-manager-version-010101-and-020101 . But When i try to create a very simple pipeline ( no jenkins and no QA) i get to the final page and when i select for sample PegaDM or Booking system architect Sample , i select Pega Sample as product and i submit the form and an error is shown as in the attached screenshot .
If i try to retry with differnet options the aplication ens with an application pipeline allready exists but i dont see any application in the devops screen . Loks like if there is a configuration that is not 100% oka and its not shown and i dont know where are the records stored to verify what is missing .
Looking in the log i see this Trace in the first atempt -->
catalina.out. & PegaRules
Hello :
I tried to follow the setup as described in this page for Pega 7.31 Platform ---> https://pdn.pega.com/deployment-manager-version-010101-and-020101/deployment-manager-version-010101-and-020101 . But When i try to create a very simple pipeline ( no jenkins and no QA) i get to the final page and when i select for sample PegaDM or Booking system architect Sample , i select Pega Sample as product and i submit the form and an error is shown as in the attached screenshot .
If i try to retry with differnet options the aplication ens with an application pipeline allready exists but i dont see any application in the devops screen . Loks like if there is a configuration that is not 100% oka and its not shown and i dont know where are the records stored to verify what is missing .
Looking in the log i see this Trace in the first atempt -->
catalina.out. & PegaRules
2018-04-09 12:29:16,881 [jsse-nio-8442-exec-2] [dalProcess] [ ] [ IecisaDe:01.01.01] (pages.DeclarativePageUtilsImpl) WARN back.stageing.pega.iecisa.com|xx.xx.xx.xx Proprietary information hidden - Required parameter'ApplicationName' for data page 'D_pxPipelineBuilds' cannot be blank.
2018-04-09 12:29:16,881 [jsse-nio-8442-exec-2] [dalProcess] [ ] [ IecisaDe:01.01.01] (pages.DeclarativePageUtilsImpl) WARN back.stageing.pega.iecisa.com|xx.xx.xx.xx Proprietary information hidden - Required parameter'ApplicationVersion' for data page 'D_pxPipelineBuilds' cannot be blank.
2018-04-09 12:31:43,980 [jsse-nio-8442-exec-3] [dalProcess] [ ] [ IecisaDe:01.01.01] (_Pipeline_Configuration.Action) ERROR back.stageing.pega.iecisa.com|xx.xx.xx.xx Proprietary information hidden - Error in Obj-Open
com.pega.pegarules.pub.database.BadClassDefinitionException: Attempting to access a rule with a bad defined-on class: PEGA-PIPELINE-CD-PEGADM0710.
at com.pega.pegarules.data.internal.access.RuleResolver.lookupFirstLevelCandidates(RuleResolver.java:2342) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.RuleResolver.getFirstLevelCandidates(RuleResolver.java:1919) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.RuleResolver.getFirstLevelCandidates(RuleResolver.java:1824) ~[prprivate.jar:?]
Accepted Solution
IECISA
ES
Hi :
Just saving as the application definition with a new version number worked . with a new version
Pegasystems Inc.
IN
Hi
Could you try creating a new pipeline by giving a new application name and version for which you havent tried creating a pipeline.
Also make sure that you have atleast 1 unlocked ruleset in your deployment manager application(lecisaDeploymentManager)
IECISA
ES
Hi i verified out that IecisaDe:01-01 is unlocked .
This aplication has this rulesets -->
IecisaDeInt:01-01
OLE1JM:01-01
OLE1JMInt:01-01
Pega-API:07-10
The deployment manager aplication includes UIKit Pega Deployment Manager and pega Devops aplications .
I tried with a new application but as i did not made any changes the error is the same :-) .
Any ideas ?
Pegasystems Inc.
IN
Hi,
In you orchestrator you need to have a deploymnet manager application(lecisaDeploymentManager).This should be built on PegaDeploymentManager.This alone should be sufficient.Please make sure that lecisaDeploymentManager application is unlocked.
If this did not solve your issue could you please share your logs and tracer dumps
On a sidenote why is Pega-API:07-10 added to the lecisaDeploymentManager application?
IECISA
ES
Hi :
Before touching anithing i triad the request aproval and it works . But i still have problems with the old applications . I will proceed to do the sugested changes and tell you more . 
IECISA
ES
Hi :
I cleaned the aplication and i could also deploy the service Request application but the redeployment of old applications still dosent work .
Ill wait to have a new version of the aplication to see if it solves the problem . I will write a note if it works .
Coforge
IN
Hi
May I know which application you did a save as new application version? Is it the lecisaDeploymentManager application? I do have a release specific application of version 01.01.01. Now as my actual enterprise application changed and updated to a new version 01.01.02 my release pipeline (which was built on the older enterprise application) is not working anymore. Are there any specific setting you did for that? Please do let me know. Thanks
Pegasystems Inc.
IN
Hi,
You would have to modify / update the application details in the release pipeline of deployment manager (orchestrator).
Click open the pipeline, opt for Actions --> Application Details and update the application version here.
Coforge
IN
Hi,
I'm not able to see Application Details option under Actions in my pipeline. Am I looking into the wrong place? Please find the screenshot attached.
Also please note I'm using Pega 7.3.1, PegaDeploymentManager 02.01.02 and PegaDevOpsFoundation 02.02.01.
Pegasystems Inc.
IN
Hi Abhishek,
Iam assuming that you have created a pipeline for NMQ 01.01.01 . Now your requirement is you want to manage pipeline for different version of NMQ(ex 02.01.01).
If this is your use case then you will have to create a new pipeline for that application version.
In 7.3.1 pipeline is unique to application version.
If this is not your use case please elaborate more on your use case