Question

16
Replies
448
Views
ChennaReddyM Member since 2013 20 posts
Accenture
Posted: 4 years ago
Last activity: 4 years 8 months ago
Closed

Information required for Build automation

Hi,

We completed Deployment Automation for our client using Utils script from Pega and some parametrized script (Shell script).

Now need to start Build automation.

I can see a lot options in prpcUtils.properties for export / create a deployment package.

Can some one give me some scenarios like..

Is it possible to create a deployment package using only RuleSet Name & Version in prpcUtils.properties? (Multiple RuleSet Names & Versions).

If it is not possible , What are the mandatory inputs / parameters we are supposed to mention in prpcUtils.properties file ?

Please find the below highlightedparameters from Export / build part from prpcUtils.properties file.

############################### SETTINGS FOR EXPORT TOOL ##########################

###################################################################################

# FULL PATH  TO ARCHIVE (REQUIRED) :

export.archive.full.path=

# Identify a Rule-Admin-Product instance by its pzInsKey (EXPORT RAP only)

export.archive.productkey=

# CLASSES TO INCLUDE (REQUIRED -- if not specifying a product key):

#       classes.included :      classes to include, separate classes by commas (no spaces)

#       included.descendent :   true (include descendants)

#   NOT required if exporting a list of pzInsKeys

export.classes.included=

export.included.descendent=true

# CLASSES TO EXCLUDE

#       classes.excluded :      classes to exclude, separate classes by commas (no spaces)

#       excluded.descendent :   true (exclude descendants)

#       For example, if including classes with descendants (Rule-) you can use this

#               to filter specific classes

export.classes.excluded=

export.excluded.descendent=true

# RULESET VERSION RANGE :

#  Specifies a minimum RuleSet version for Rule Resolved instances

#  of Rule- (e.g. 05- or 05-01-01)

export.startVersion=

export.endVersion=

#  Full path to a file which contains instances to export

#        identified by pzInsKey, 1 per line.

#  if exporting a list of pzInsKeys, do not provide other arguments such as export.classes.included

export.keys.file=

# RULESET NAME :

#  Include instances of this RuleSet (for Rule- classes). This is case sensitive (e.g. pass Pega-Desktop, not pega-desktop)

export.ruleset.name=

# Specify application name (only one) with version for exporting ABV ruleset in this application's context.

# For example, PegaRULES!07.10

export.application.context=

#  Preserve lock property on checked out instances

# Only use if moving the corresponding locked instance

export.preserve.locks=false

# MIGRATION EXPORT :

# Both of the following properties are required for a migration export

#

# full-path to the XML File containing classes to export

# example: export.migration.xml=C:/users/administrator/exportClasses.xml

export.migration.xml=

# export all instances created or updated after, uses format: YYYY MM DD hh mm ss S a

# example: for March 15, 2012 04:42:00:0 PM, set export.migration.date="2012 03 15 04 42 00 0 PM"

export.migration.date=

Data Integration
Moderation Team has archived post
Share this page LinkedIn