Question

6
Replies
138
Views
FrankJ11 Member since 2016 4 posts
Scotiabank
Posted: 2 years ago
Last activity: 1 year 10 months ago
Closed

Devops stucked exporting / moving the file from Pega 7.3.1 Multitenancy

Hi Support,

we are trouble-shooting an issue of exporting product from DEV Pega 7.3.1 Multitenancy to QA multitenancy.

Background:

first time working on Multi-tenancy pega 7.3.1, same Jenkins pipeline works well on single tenenacy Pega 7.3.1. we are simulate the approach documented at https://community.pega.com/knowledgebase/articles/using-prpcserviceutils-and-jenkins-automated-application-deployment

and first thing we do is exporting the shared / TOM layer as Product Zip file and try to move it to QA.

1. the ZIP file was generated on the Pega Server, seems completed / successfully.

2. the DEV pega log has " Operation Status: Finalizing the EIAP-01.01.01.zip archive -- please wait..."

3. the ZIP file was generated, transferred to PC and was opened there by WinZip successfully.

the problem:

the Jenkins script initially had 2 or 3 times of response as below:

java] 13:08:33.079 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-ltmpldes-LATAM_CL_PEGA-pega-build-pipeline-41: Parsing response
[java] 13:08:33.079 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-ltmpldes-LATAM_CL_PEGA-pega-build-pipeline-41: Parsing response of length 782
[java] 13:08:33.081 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-ltmpldes-LATAM_CL_PEGA-pega-build-pipeline-41: Parsing content of type application/xml; charset=UTF-8

and then it timed out while all following response as below:

[java] 13:10:38.751 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-ltmpldes-LATAM_CL_PEGA-pega-build-pipeline-41: Parsing response
[java] 13:10:38.752 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-ltmpldes-LATAM_CL_PEGA-pega-build-pipeline-41: Parsing response of length null
[java] 13:10:38.754 [pool-2-thread-1] INFO [egarules.serviceclient.rest.RestResponse] - jenkins-ltmpldes-LATAM_CL_PEGA-pega-build-pipeline-41: Parsing content of type multipart/form-data; boundary=GAiQI7mizE1jpnqWi5w-AMeyTFPc4zM

question:

1. is it still proper approach to use prpcServiceUtils and Jenkins for Pega 7.3.1 Multi-tenancy ?

2. is there any "extra", "special steps" for v7.3.1 or Multi-tenancy by using prpcServiceUtils + Jenkins ?

3. if Pega product code has been locked and no more change, the exported ZIP file should always be the same size over the following time? currently, the ZIP files size are always different no mater manual export or automated export.

BTW, log file was attached

Thanks !

Frank

***Edited by Moderator Marissa to update SR Details***

DevOps SR Created
Moderation Team has archived post
Share this page LinkedIn