DevOps Pipeline instance is not moving to next stage
Currently I'm setting up a devops pipeline in my local machine. I have set up DEV & RM in one system and DEV repository and QA in the another system
I'm using JFrog Artifactory repository for the repository and tested the connectivity from dev and QA.
Defined the authentication profiles and DSS appropriately.
But still my pipeline instance is not moving to next stage.
LOGS
2018-06-12 11:23:14,954 [Admin.RM] [GoOrganic01.01.01] [GoOrganic_010101_6] INFO Logs of CICD build. BuildID: PEGA-PIPELINE-CD GO-14, Branch list: Empty
2018-06-12 11:23:15,076 [Admin.RM] [GoOrganic01.01.01] [GoOrganic_010101_6] INFO Build NEW, Build ID:GO-14
2018-06-12 11:23:15,128 [Admin.RM] [GoOrganic01.01.01] [GoOrganic_010101_6] INFO Build is moved to new stage:Development
2018-06-12 11:23:15,195 [Admin.RM] [GoOrganic01.01.01] [GoOrganic_010101_6] INFO New task started. Task name:Publish, in stage:Development
2018-06-12 11:23:15,339 [Admin.RM] [GoOrganic01.01.01] [GoOrganic_010101_6] ERROR Publish task failed. Reason:
I very much appreciate you're input to resolve this issue.
Accepted Solution
AI4Process
GB
Thanks CarissaW, The error on publish build has been resolved and the pipeline instance has moved to QA stage.
Now the build is successfully published to the repository.
The issue is - I have provided the dev env URL in the following format http://x.x.x.x:yyyy
after changing to http://x.x.x.x:yyyy/prweb the publish task was successful.
Now the deployment task is failing due to
ava.lang.RuntimeException: org.apache.http.conn.HttpHostConnectException: Connect to x.x.x.x:8080 [/x.x.x.x] failed: Connection timed out
NB: The repository connectivity status is success.
Could you please help to resolve this issue
Pegasystems Inc.
US
Are there any additional error messages in the PegaRULES log file to show why the Publish task failed?
Updated: 20 Jun 2018 10:03 EDT
AI4Process
GB
I traced RULE-OBJ-ACTIVITY PEGA-PIPELINE-CD PZPUBLISHRAP and the service http://xx.xx.xx.xx:8080/PRRestService/cicd/v1/task/publish has returned
| pyStatusValue | Fail: The server indicated that there is no resource at the endpoint. |
| pyStatusMessage | the server responded with an HTTP 404 code, indicating that the resource does not exist. |
The request payload
{
"pxObjClass":"Pega-Int-Pipeline" ,
"pyApplicationName":"GoOrganic" ,
"pyApplicationVersion":"01.01.01" ,
"pyBuildArtifactName":"GoOrganic_010101_23.zip" ,
"pyCallBackURL":"http://localhost:8080/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask" ,
"pyDoPackage":"true" ,
"pyID":"PEGA-PIPELINE-CD GO-31" ,
"pyProductName":"GoOrganic" ,
"pyProductVersion":"20180606.130138" ,
"pyRepositoryName":"Repo1"
}
NB: The Repository connectivity status is success!!
Please let me know if I'm missing anything.
Cognizant
US
Hi Tharine,
Is this issue because of referring env url like 'http://localhost:8080' format ? even I am facing these issue, I have given ''http://localhost:8080/prweb'' format.
-Required parameter'ApplicationName' for data page 'D_pxPipelineBuilds' cannot be blank.
- Required parameter'ApplicationVersion' for data page 'D_pxPipelineBuilds' cannot be blank.
- Invalid JSON request. Reason : JSON text must start with '{' or '[' at 0 [character 1 line 1]
Thanks,
Sudheer Nimmagadda.
Updated: 21 Jun 2018 11:30 EDT
Pegasystems Inc.
US
I reviewed the document with your analysis. I have the version in Pega-DevOps-Foundation:03-01-01 installed in my system and see the parameters have been updated in the REST service to Param.TaskName and Param.Status.
I reviewed the document with your analysis. I have the version in Pega-DevOps-Foundation:03-01-01 installed in my system and see the parameters have been updated in the REST service to Param.TaskName and Param.Status.
AI4Process
GB
Pega-DevOps-Foundation 03-01-01 is for Pega 7.4 platform, that means are there any hotfixes available for Pega 7.3.1 DevOps?
Can I use Pega-DevOps-Foundation 03-01-01 with Oega 7.3.1 platform?
I have followed https://community.pega.com/knowledgebase/articles/installing-and-configuring-deployment-manager-1xx-and-2xx
Herewith I have attached the steps I have followed with the screeshots , Please let me know if I have missed anything?
Thank you
Updated: 25 Jun 2018 8:40 EDT
Pegasystems Inc.
US
I don't have the specifics on that so we'll have to let someone with more expertise in this area respond.
Accepted Solution
AI4Process
GB
Thanks CarissaW, The error on publish build has been resolved and the pipeline instance has moved to QA stage.
Now the build is successfully published to the repository.
The issue is - I have provided the dev env URL in the following format http://x.x.x.x:yyyy
after changing to http://x.x.x.x:yyyy/prweb the publish task was successful.
Now the deployment task is failing due to
ava.lang.RuntimeException: org.apache.http.conn.HttpHostConnectException: Connect to x.x.x.x:8080 [/x.x.x.x] failed: Connection timed out
NB: The repository connectivity status is success.
Could you please help to resolve this issue
Cognizant
US
Deployment task failing in Dev or QA ?
Check your target systems log file for any DevOps related exceptions,Hope you configured "RMURL" DSS in all systems.
AI4Process
GB
This issue is resolved!,
Issues:
My QA system got crashed due to postgrest connectivity failure, after installing a fresh instance of Pega 7.3.1 PE to resemble QA system the issue got resolved.
And the call back from deployment in QA to RM was failing because the call back URL has got constrcuted with "localhost" instead of RM system's IP address, after defining a new pipline instance with all the URLs to be set to IP address the issue got resolved.
Now the build is successfully getting deployed to QA from Dev on manual trigger of the pipeline instance!!
Ernst & Young LLP
IN
Hi,
Could you please let me know why I am getting below error while starting my deployment . I am using V 7.4
"Error: Attempting to access a rule with a bad defined-on class: Pega-Pipeline-CD-DevOpsDevOps. problem encountered when opening instance RULE-OBJ-CASETYPE PEGA-PIPELINE-CD-DEVOPSDEVOPS "
Basically I am having application called "DEVOPS" in my Dev system and I am trying to deploy this application to staging , so while giving application details in pipeline configuration I mentioned Application name == DevOps and Product name == DevOps and Version == 01.01.01.
Please let me where I am doing wrong.
Regards,
Sowmya
Rulesstack Solutions LTD
US
I am using 7.3 and facing the same issue the build is deploying in jfrog but unable to push it to next environment. In my case Orchestration server and dev server is the same.
its quite strange as the same rest service works for pushing the build but then it says invalid repository. Any ideas on this?
I am using 7.3 and facing the same issue the build is deploying in jfrog but unable to push it to next environment. In my case Orchestration server and dev server is the same.
its quite strange as the same rest service works for pushing the build but then it says invalid repository. Any ideas on this?
2019-05-16 16:41:53,106 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Logs of CICD build. BuildID: PEGA-PIPELINE-CD SU-47, Branch list: Empty
2019-05-16 16:41:53,199 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Build NEW, Build ID:SU-47
2019-05-16 16:41:53,231 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Build is moved to new stage:Development
2019-05-16 16:41:53,294 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO New task started. Task name:Publish, in stage:Development
=============== Beginning of remote server logs for task: publish, Server:Development ===============
2019-05-16 21:41:53,453 [PegaRULES-Batch-90] [Rule_Obj_Activity.pzCreateTaskWrapper.Pega_Int_Pipeline.Action] INFO Task execution started for task type: publish
Request object: {
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"Sup_Toggle"
,"pyApplicationVersion":"02.01.01"
,"pyBuildArtifactName":"Sup_Toggle_020101_47.zip"
,"pyCallBackURL":"https://localhost:8080/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask"
,"pyDoPackage":"true"
,"pyID":"PEGA-PIPELINE-CD SU-47"
,"pyProductName":"ToggleSample"
,"pyProductVersion":"01.01.01"
,"pyRepositoryName":"Jfrog"
}
2019-05-16 21:41:53,997 [PegaRULES-Batch-90] [Rule_Obj_Activity.CreateZipFile.Rule_Admin_Product.Action] INFO Setting Clear Locks***********************************
2019-05-16 21:41:53,997 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Operation Status: Exporting Inventory
2019-05-16 21:41:54,013 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Operation Status: Export Complete
2019-05-16 21:41:54,013 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Exported 3 instance(s)
2019-05-16 21:41:54,180 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Operation Status: Constructing export file -- please wait...
2019-05-16 21:41:54,183 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Operation Status: Constructing export file -- please wait....
2019-05-16 21:41:54,183 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Operation Status: Constructing export file -- please wait.....
2019-05-16 21:41:54,183 [PegaRULES-Batch-90] [com.pega.pegarules.deploy.internal.util.MoveLog] INFO Operation Status: Constructing export file -- please wait......
2019-05-16 21:41:55,140 [PegaRULES-Batch-90] [Rule_Obj_Activity.pzCreateTaskWrapper.Pega_Int_Pipeline.Action] INFO Task execution completed for task : publish
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"Sup_Toggle"
,"pyApplicationVersion":"02.01.01"
,"pyBuildArtifactName":"Sup_Toggle_020101_47.zip"
,"pyCallBackURL":"https://localhost:8080/prweb/PRRestService/cicd/v1/task/publish/status?FlowName=pzPublishRAP&FlowActionName=pzPauseTask"
,"pyDoPackage":"true"
,"pyID":"PEGA-PIPELINE-CD SU-47"
,"pyProductName":"ToggleSample"
,"pyProductVersion":"01.01.01"
,"pyRepositoryName":"Jfrog"
,"pyStatusMessage":"Artifact is successfully published to the repository."
,"pyStatusValue":"SUCCESS"
,"pyBuildArtifact":{
"pxObjClass":"Data-Artifact"
,"pyArchiveName":"Sup_Toggle_020101_47.zip"
,"pyArtifactName":"Sup_Toggle"
,"pyName":"Sup_Toggle_020101_47.zip"
,"pySize":"12484"
,"pyTargetLocation":"/application/Sup_Toggle_02.01.01/Sup_Toggle_020101_47/Sup_Toggle_020101_47.zip"
,"pyType":"application"
}
}
=============== End of remote server logs for task: publish, Server:Development ===============
2019-05-16 16:41:57,262 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Remote task execution completed.
2019-05-16 16:41:57,303 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Task Generating build got COMPLETED. Start time:2019-05-16 16:41:53, End time:2019-05-16 16:41:57, Time taken:0.07 mins
2019-05-16 16:41:57,378 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Development stage got COMPLETED. Enter time:2019-05-16 16:41:53, Exit time:2019-05-16 16:41:57, Time taken:0.07 mins
2019-05-16 16:41:57,429 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Build is moved to new stage:Quality Assurance
2019-05-16 16:41:57,443 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO New task started. Task name:Deploy, in stage:Quality Assurance
=============== Beginning of remote server logs for task: deploy, Server:Quality Assurance ===============
2019-05-16 21:41:57,731 [PegaRULES-Batch-67] [Rule_Obj_Activity.pzCreateTaskWrapper.Pega_Int_Pipeline.Action] INFO Task execution started for task type: deploy
Request object: {
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"Sup_Toggle"
,"pyApplicationVersion":"02.01.01"
,"pyBuildArtifactName":"Sup_Toggle_020101_47.zip"
,"pyCallBackURL":"https://localhost:8080/prweb/PRRestService/cicd/v1/task/deploy/status?FlowName=pzDeployRAP&FlowActionName=pzPauseTask"
,"pyID":"PEGA-PIPELINE-CD SU-47"
,"pyRepositoryName":"Jfrog"
,"pyDependencies":[ ]
}
2019-05-16 21:41:57,733 [PegaRULES-Batch-67] [Rule_Obj_Activity.pzCreateTaskWrapper.Pega_Int_Pipeline.Action] INFO Task execution completed for task : deploy
Posting status to release manager system. Status object:
{
"pxObjClass":"Pega-Int-Pipeline"
,"pyApplicationName":"Sup_Toggle"
,"pyApplicationVersion":"02.01.01"
,"pyBuildArtifactName":"Sup_Toggle_020101_47.zip"
,"pyCallBackURL":"https://localhost:8080/prweb/PRRestService/cicd/v1/task/deploy/status?FlowName=pzDeployRAP&FlowActionName=pzPauseTask"
,"pyID":"PEGA-PIPELINE-CD SU-47"
,"pyRepositoryName":"Jfrog"
,"pyStatusMessage":"Invalid Repository / Repository does not exist "
,"pyStatusValue":"FAILED"
,"pyDependencies":[ ]
}
=============== End of remote server logs for task: deploy, Server:Quality Assurance ===============
2019-05-16 16:41:59,804 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Remote task execution completed.
2019-05-16 16:41:59,848 [Sam Rayi] [Sup_Toggle02.01.01] [Sup_Toggle_020101_47] INFO Task Deploy got ERROR. Start time:2019-05-16 16:41:57, End time:2019-05-16 16:41:59, Time taken:0.03 mins
Updated: 16 May 2019 22:30 EDT
Pegasystems Inc.
IN