Question

1
Replies
424
Views
ParmeetSinghH Member since 2015 7 posts
Infosys Limited
Posted: 1 year ago
Last activity: 1 year 7 months ago
Closed

Circular dependency detected

Dear All,

On creating a pipeline i tried to executed the deployment and no response on screen but errors are like below.

I am not sure, why there is a circular dependency when my authentication profile for Release Manager on Candidate system is built on PegaDevOpsFoundation which on further is build on pegaRULES.

Any pointers?

[1/8/19 14:07:18:355 CET] 0000009a SystemOut O 2019-01-08 14:07:18,354 [ WebContainer : 21] [ STANDARD] [ ] [sFoundation:02.01.03] (ndler.Pega_Int_Pipeline.Action) INFO was00547.bc|10.121.110.40|Rest|cicd|v1|task|AECQB6F4ONFDYGBRROU6GKBBWD1W9JKER - Task status processing started. Task:publish,FlowName:pzPublishRAP, Flow action Name:pzPauseTask Build id:PEGA-PIPELINE-CD DE-5, status:FAIL, message:Internal processing error.** Circular dependency detected: PegaDevOpsFoundation:02.01.03 is built on PegaDevOpsFoundation:02.01.03 - this is not supported for applications with more than one built on application.
** Incorrect password specified.** Update record failed: ** Circular dependency detected: PegaDevOpsFoundation:02.01.03 is built on PegaDevOpsFoundation:02.01.03 - this is not supported for applications with more than one built on application.
.pyConfirmPassword: Incorrect password specified.
.
[1/8/19 14:07:18:355 CET] 0000009a SystemOut O 2019-01-08 14:07:18,355 [ WebContainer : 21] [ STANDARD] [ ] [sFoundation:02.01.03] (ndler.Pega_Int_Pipeline.Action) INFO was00547.bc|10.121.110.40|Rest|cicd|v1|task|AECQB6F4ONFDYGBRROU6GKBBWD1W9JKER - Task status processing completed. Task:publish Build id: PEGA-PIPELINE-CD DE-5
[1/8/19 14:07:18:385 CET] 0000009a SystemOut O 2019-01-08 14:07:18,385 [ PegaRULES-Batch-1] [ STANDARD] [ ] [sFoundation:02.01.03] (apper.Pega_Int_Pipeline.Action) INFO id844494a - Task execution status published by doing call back for task name:publish
Http status code of call back:200
Sattus message of call back: OK

DevOps
Moderation Team has archived post
Share this page LinkedIn