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

 Samanth Reddy Chintakuntla (SamanthReddy)
JPMorgan Chase
Software Engineering
JPMorgan Chase
US
SamanthReddy Member since 2017 3 posts
JPMorgan Chase
Posted: Sep 4, 2017
Last activity: Sep 6, 2017
Posted: 4 Sep 2017 0:48 EDT
Last activity: 6 Sep 2017 7:18 EDT
Closed
Solved

Exporting Product file using Jenkins fails second time

Hi

I have created a product rule, for first time I was able to export the product file using Jenkins Build successfully. However when I try with the same product rule and version without any changes, subsequent builds for export are failing.

No matching Product or Application found with inputs Product Name:TestJenkins Product Version:01-01-01

Has anyone faced this kind of issue. Any thoughts?

Thanks

Sam

***Updated by moderator: Lochan to create branched post***

To see attachments, please log in.
DevOps
System Administration

Accepted Solution

Posted: 8 years ago
Posted: 6 Sep 2017 4:34 EDT
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

Hi Samanth,

Thanks for sharing the requested information. As per the information available in the Failure.txt log file you specified below product version,

[pega:propertyfilegenerator] jenkins-PegaDeploymentDev-16.export.productVersion=01-01-01

But if you observe the Success.txt log file the product version is 01.01.01 as shown below,

[pega:propertyfilegenerator] jenkins-PegaDeploymentDev-15.export.productVersion=01.01.01

Also if you observe your Product rule the version of product is 01.01.01 not 01-01-01

Kindly change the product version to 01.01.01 then your export will work successfully.

Regards

Mahesh

To see attachments, please log in.
Posted: 8 years ago
Posted: 4 Sep 2017 20:52 EDT
Prasanth Kumar Kolluru (prasanthkumar)
PEGA
Technical Solutions Engineer
Pegasystems Inc.
IN

Did you find any errors in the build file log?

Kindly share the logs to further debugging

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 4 Sep 2017 22:57 EDT
Sudhakar Reddy Yaparla (YSudhakarReddy)
JPMorgan Chase & Company

JPMorgan Chase & Company
US

Hi,

In the configuration file in product version you need to pass the generated id instead of ruleset version. I hope it will resolve.

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Sep 2017 11:39 EDT
Samanth Reddy Chintakuntla (SamanthReddy)
JPMorgan Chase
Software Engineering
JPMorgan Chase
US

Hi

I am not passing ruleset version. When I create a product rule, say TestJenkins  I am giving the product version as 01-01-01. I think it should be correct. I did not understand " you need to pass the generated id instead of ruleset version" Can you explain more on this?

 

Thanks

Sam

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Sep 2017 3:33 EDT
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

Hi Samanth,

The product version is not 01-01-01, kindly check the attachment where you can find the product version. In my Jenkins Product version is 20170802.085237.

So correct the product version and try the build it will work.

Regards

Mahesh

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Sep 2017 11:44 EDT
Samanth Reddy Chintakuntla (SamanthReddy)
JPMorgan Chase
Software Engineering
JPMorgan Chase
US

Hi

Thank you for response.

Product version can be 01-01-01(attaching image FYR). There is no rule to be any specfic number. You can check the product versions given by Pega. Attaching sample. Also my question was first time it ran successfully and I got the zip file. When I run the build for same product without any changes its not working.

Thanks

Sam

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Sep 2017 12:16 EDT
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

@Samanth - if you don't mind can you share your Product rule screenshot along with the console output of your jenkins build for further investigation.

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Sep 2017 21:05 EDT
Samanth Reddy Chintakuntla (SamanthReddy)
JPMorgan Chase
Software Engineering
JPMorgan Chase
US

Hi

Uploaded Jenkins log's for success and failure scenario. Product rule screenshot.

 

Thanks

Sam

To see attachments, please log in.

Accepted Solution

Posted: 8 years ago
Posted: 6 Sep 2017 4:34 EDT
Mahesh Midthuru (Mahesh Midthuru)
PEGA
Senior Principal Application Engineer, Customer Service Digital
Pegasystems Inc.
US

Hi Samanth,

Thanks for sharing the requested information. As per the information available in the Failure.txt log file you specified below product version,

[pega:propertyfilegenerator] jenkins-PegaDeploymentDev-16.export.productVersion=01-01-01

But if you observe the Success.txt log file the product version is 01.01.01 as shown below,

[pega:propertyfilegenerator] jenkins-PegaDeploymentDev-15.export.productVersion=01.01.01

Also if you observe your Product rule the version of product is 01.01.01 not 01-01-01

Kindly change the product version to 01.01.01 then your export will work successfully.

Regards

Mahesh

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