Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US
Mr. Ravi Kumar Pisupati Member since 2024 90 posts
GovCIO
Posted: Dec 20, 2019
Last activity: Dec 22, 2019
Posted: 20 Dec 2019 3:00 EST
Last activity: 22 Dec 2019 16:19 EST
Closed
Solved

Got an err while integrating with Jenkins from Pega V722

Hi,

I have followed the below PDN article strictly to setup Jenkins integration using Pega 7.2.2 (Dev env).

https://community.pega.com/knowledgebase/articles/using-prpcserviceutils-and-jenkins-automated-application-deployment

I am getting the below err while deploying the code. Attached the settings and the err details too.

Jenkins version:2.209

JDK:1.8.0_121

ANT version: apache-ant-1.10.7

==================================

[jenkins] $ cmd.exe /C "ant.bat -file Jenkins-build.xml -DproductVersion=01.01.01 -DproductName=HRServicesRAP exportprops && exit %%ERRORLEVEL%%"
'ant.bat' is not recognized as an internal or external command,
operable program or batch file.
Build step 'Invoke Ant' marked build as failure
Finished: FAILURE

===============================

Can any expert in this area help me?

Thanks,

Ravi Kumar.

To see attachments, please log in.
Pega Platform Low-Code App Development Dev/Designer Studio Java and Activities Data Integration DevOps System Administration

  • ADITYA KORALE Narasimha Reddy Saravana Kumar G

Accepted Solution

Posted: 4 years ago
Posted: 22 Dec 2019 16:17 EST
Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US

Hi All,

This is to inform that my issue got resolved after setting up this whole process from fresh and that too this time I have used my personal laptop. Due to firewall or permissions issue from my office laptop, I couldn't succeed earlier and I was seeing all the mentioned issues. Now I am good and I was able to push the code from V722/V8.1 (source) to V722/V8.1(target). Hoping that "prpcserviceutils" file version is not a matter based on my observation. The main cautious piece over here is the proper settings, proper permissions in the laptop and enough speed of the system to run ANT,Jenkins without any delays/timeout issues. Thanks for all the folks who helped me in this regards,

Regards,

Ravi Kumar

To see attachments, please log in.
Posted: 4 years ago
Posted: 20 Dec 2019 17:16 EST
Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US

Thank you Srikant. The mentioned error is gone and I got a new err after following your document. Here is the err and my Jenkins settings for Pega V8.3 (localhost). Please check and correct me where I went wrong.

=======================

Show More

Thank you Srikant. The mentioned error is gone and I got a new err after following your document. Here is the err and my Jenkins settings for Pega V8.3 (localhost). Please check and correct me where I went wrong.

=======================

-processInstances:
     [echo] Performing export on multiple instance(s)
[pega:echoargline] arg line : -action export -propFileDir C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils/generated -poolSize ${prpcserviceutils.pool.size} -requestTimeOut ${prpcserviceutils.request.timeout} -tempDir C:\Windows\TEMP\/PegaInstallTemp-20-December-2019-13.49.04 -artifactsDir C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaCodeDeployment -processFailStrategy FAIL_PROCESS_ON_SINGLE_SYSTEM_FAILURE
     [echo] Reading connection information from C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaCodeDeployment\jenkins-PegaCodeDeployment-24_export.properties

BUILD FAILED
C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils\prpcserviceutilsWrapper.xml:179: Connection Property file C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaCodeDeployment\jenkins-PegaCodeDeployment-24_export.properties is not a valid file

Total time: 2 seconds
Exiting with Error

Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE

Show Less
To see attachments, please log in.
Posted: 4 years ago
Posted: 21 Dec 2019 7:41 EST
Srikanth Kasula (SrikanthKasula) EAI Systems Senior Consultant
EAI Systems
SG

Hi Ravi Kumar,

Refer the below article where i have clearly documented E2E process.

https://collaborate.pega.com/discussion/automating-pega-deployments-using-jenkins-and-prpcserviceutils-tool

Let me know if you have any other issues on top of this.

Thanks,

Srikanth

 

To see attachments, please log in.
Posted: 4 years ago
Posted: 21 Dec 2019 20:03 EST
Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US

Hi Srikanth,

I have followed the article and I was successful in integrating Jenkins with V83 (localhost) and I saw build was successful. But I checked the target:localhost system and the code is not deployed though build was successful from the console log. In my case both source and target are V83 localhost instance only. Please let me know on why I didn't see the code deployed in target env.

Show More

Hi Srikanth,

I have followed the article and I was successful in integrating Jenkins with V83 (localhost) and I saw build was successful. But I checked the target:localhost system and the code is not deployed though build was successful from the console log. In my case both source and target are V83 localhost instance only. Please let me know on why I didn't see the code deployed in target env.


 
[EnvInject] - Injecting as environment variables the properties content ImportExistingInstance=override ARTIFACTS_DIR=C:/Users/rpisupat/Documents/JenkinsIntegPega [EnvInject] - Variables injected successfully. [jenkins] $ cmd.exe /C "C:\Users\rpisupat\Documents\JenkinsIntegPega\Ant\apache-ant-1.10.7\bin\ant.bat -file Jenkins-build.xml -DapplicationVersion=01.01.01 -DproductVersion=01.01.01 -DTargetHost=https://localhost:8080 -DTargetPassword=rules -DproductName=HRServicesRAP -DapplicationName=HRServices -DTargetUser=HRAdmin exportprops && exit %%ERRORLEVEL%%" 
Buildfile: C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\samples\jenkins\Jenkins-build.xml

exportprops:

[propertyfile] Creating new property file: C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils\jenkins-PegaV83ExportImportRAP-6_export.properties

BUILD SUCCESSFUL
Total time: 15 seconds

[PegaV83ExportImportRAP] $ cmd /c call C:\Windows\TEMP\jenkins6038166514587297634.bat

C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaV83ExportImportRAP>C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils\prpcServiceUtils.bat export --connPropFile C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaV83ExportImportRAP\jenkins-PegaV83ExportImportRAP-6_export.properties --artifactsDir C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaV83ExportImportRAP 

[jenkins] $ cmd.exe /C "C:\Users\rpisupat\Documents\JenkinsIntegPega\Ant\apache-ant-1.10.7\bin\ant.bat -file Jenkins-build.xml -DapplicationVersion=01.01.01 -DproductVersion=01.01.01 -DTargetHost=https://localhost:8080 -DTargetPassword=rules -DproductName=HRServicesRAP -DapplicationName=HRServices -DTargetUser=HRAdmin importprops && exit %%ERRORLEVEL%%"

Buildfile: C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\samples\jenkins\Jenkins-build.xml

importprops:

     [copy] Copying 1 file to C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\destination
[propertyfile] Creating new property file: C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils\jenkins-PegaV83ExportImportRAP-6_import.properties

BUILD SUCCESSFUL
Total time: 2 minutes 57 seconds

[PegaV83ExportImportRAP] $ cmd /c call C:\Windows\TEMP\jenkins2637485643329802037.bat

C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaV83ExportImportRAP>C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils\prpcServiceUtils.bat export --connPropFile C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaV83ExportImportRAP\jenkins-PegaV83ExportImportRAP-6_export.properties --artifactsDir C:\Users\rpisupat\Documents\JenkinsIntegPega\workspace\PegaV83ExportImportRAP 

Finished: SUCCESS

Show Less
To see attachments, please log in.
Posted: 4 years ago
Posted: 22 Dec 2019 4:19 EST
Srikanth Kasula (SrikanthKasula) EAI Systems Senior Consultant
EAI Systems
SG

Hi Ravi Kumar,

1. Might be both Source and Target env are same, can you try with having both source and target are different.

2.Can you share build.xml file,export and import property files generated by successful build for further debugging.

Thanks,

Srikanth

To see attachments, please log in.
Posted: 4 years ago
Posted: 22 Dec 2019 16:19 EST
Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US

Hi Srikanth,

I am good to go now. As I mentioned my final reply to this post, all issues are related to my office laptop's permissions issue. Same exercise working in my personal laptop and no issues so far. It is the time for me to play on setting the Pipelines and the scheduling of the jobs from Jenkins. Lot more work is there to focus :) 

Thanks,

Ravi Kumar.

To see attachments, please log in.
Posted: 4 years ago
Posted: 21 Dec 2019 3:25 EST
Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US

Hi all,

I have followed the below article and changed the settings for my Jenkins integration but still I am getting the issue.

https://collaborate.pega.com/discussion/procedure-export-import-using-prpcserviceutils-jenkins-pega-v722

BUILD FAILED
C:\Users\rpisupat\Documents\JenkinsIntegPega\Pega\prpcServiceUtils_v83\scripts\utils\prpcserviceutilsWrapper.xml:179: Connection Property file -Dprpc.service.util.action=export is not a valid file

Total time: 4 seconds
Exiting with Error

Build step 'Execute Windows batch command' marked build as failure
Finished: FAILURE

 

To see attachments, please log in.

Accepted Solution

Posted: 4 years ago
Posted: 22 Dec 2019 16:17 EST
Ravi Kumar Pisupati (Mr. Ravi Kumar Pisupati) GovCIO Pega Lead Solutions Architect
GovCIO
US

Hi All,

This is to inform that my issue got resolved after setting up this whole process from fresh and that too this time I have used my personal laptop. Due to firewall or permissions issue from my office laptop, I couldn't succeed earlier and I was seeing all the mentioned issues. Now I am good and I was able to push the code from V722/V8.1 (source) to V722/V8.1(target). Hoping that "prpcserviceutils" file version is not a matter based on my observation. The main cautious piece over here is the proper settings, proper permissions in the laptop and enough speed of the system to run ANT,Jenkins without any delays/timeout issues. Thanks for all the folks who helped me in this regards,

Regards,

Ravi Kumar

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice