IBM / dbb-zappbuild

zAppBuild is a generic build solution for building z/OS applications using Apache Groovy build scripts and IBM Dependency Based Build (DBB) APIs.
Apache License 2.0
41 stars 140 forks source link

Deletion logic not ready for different output librarys during Transfer #272

Open nixpix49 opened 1 year ago

nixpix49 commented 1 year ago

We have decided to set the property documentDeleteRecords=true in order to handle deletions in our pipeline. I understand the flow for Cobol, LinkEdit etc since they exist as langPrefix in BuildUtilities.groovy (langPrefix_outputDatasets).

However, I don't understand the flow for 'transfers'.

We have a setup like this, in Transfer.grooovy: transfer_srcPDS=${hlq}.SOURCE transfer_clistPDS=${hlq}.CLIST transfer_xmlPDS=${hlq}.XML ... ...

According to the docs , I can't use transfer_outputDatasets, since our stuff is divided into more than one dataset.

Info in README in zAppBuild/build-conf: transfer_outputDatasets - List of output datasets to document deletions Can be overridden by a file property. If used for multiple, use a file property to set transfer_outputDatasets

How should I define the file.properties needed ? Should I create a separate file for each of our definitions mentioned above, like SOURCE.properties ? Naming convention for this file to be able to pick it up ? Should I put it in the Transfer.properties file ? Name/content of property ?

Hope you understand what I'm trying to say here...

Thanks