zAppBuild 3.3.0

New & Noteworthy

This release delivers a new strategy for files that don't need to be scanned but are processed by language scripts - such as JCLs, XML files or other configuration files. Starting with this release, zAppBuild is only scanning a file for its dependencies when the file extension is specified it in the dbb.scannerMapping property. The property mapping, being located in build-conf/defaultzAppBuildConf.properties, is carrying the default mappings. Important: If you have a requirement to scan files with different file extensions, please add them to the configuration. Independently of the scanner mapping, files will continue to be recorded as logical files in the collections.

The test framework was significantly updated and is now easier to use and also to extend with your own test bucket.

What's Changed

• Strategy to record logical files but skip scanning them by @dennis-behm in #30
• Tolerate old dbb.scannerMapping configurations by @dennis-behm in #385
• Avoid additional scan of build file during impact analysis by @dennis-behm in #371
• Refactoring Test Framework by @dennis-behm in #363
• Ability to maintain consistent information in the DBB metadata store for dependencies on generated zunit test case by @dennis-behm in #368
• Fix condition evaluating generated test cases and zunit processing by @dennis-behm in #382
• Fix sorting of build list when creating test case dependency programatically by @dennis-behm in #364
• Skip inspecting load modules when running in preview mode by @dennis-behm in #387
• Release zAppBuild 3.3.0 by @dennis-behm in #360

Full Changelog: 3.2.0...3.3.0

zAppBuild v3.2.0

New & Noteworthy

This release of zAppBuild is adding some end-user enhancements such as a progress indicator on processing the build files mapped to a language script:

*** (1/3) Building file zopeneditor-sample/COBOL/SAM1.cbl
*** (2/3) Building file zopeneditor-sample/COBOL/SAM1LIB.cbl
*** (3/3) Building file zopeneditor-sample/COBOL/SAM2.cbl

Or the ability to display file attributes and their overrides (3rd line) :

*** (4/6) Building file MortgageApplication/cobol/epscsmrt.cbl
....
Program attributes: CICS=true*, SQL=false, DLI=false, MQ=false
Cobol compiler parms for MortgageApplication/cobol/epscsmrt.cbl = LIB,CICS
Link-Edit parms for MortgageApplication/cobol/epscsmrt.cbl = MAP,RENT,COMPAT(PM5),SSI=85e0df0e

A new supplemental build option --preview to run a build without doing actually processing the build list to allow users with the insights, what would be done. Please read more about it in BUILD.md

The zAppBuild Testframework got extended with a new application for some sample Assembler sources.

The languages processing scripts Transfer.groovy and Assembler.groovy were enhanced. Transfer.groovy is now capable of processing files which require different dataset characteristics. The --debug flag was introduced in Assembler.groovy to produce a debug side file (to be used with the IBM Problem Determination tools) along with some bug fixes.

The reporting capabilities got refactored to use the updated DBB 2.0 API.

What's Changed

• Uplift Transfer.groovy script by @dennis-behm in #328
• Refactor zAppBuild reporting capabilities by @dennis-behm #341
• Fix load libraries for scanning for link dependencies by @dennis-behm in #334
• Preview build option by @dennis-behm in #347
• Ability to print file attributes and including their overrides by @dennis-behm in #343
• Fix zAppBuild test framework test script for build preview option by @dennis-behm in #355
• Uplift Assembler.groovy script by @dennis-behm in #335
• Release zAppBuild 3.2.0 by @dennis-behm in #354

Full Changelog: 3.1.0...3.2.0

zAppBuild v3.1.0

New & Noteworthy

• A new functionality is provided for file level property overrides: A language configuration allows defining multiple build properties for a set of mapped files. See details on the documentation about File Property Management in zAppBuild
• zAppBuild is leveraging the MQ file attributes of the logical file of DBB to determine automatically the required MQ stub
• The way allocations are done for object decks has changed. While previously, a temp dataset was used in most of the cases, the release is simplifying the scripts by always storing the object deck in an object deck dataset.
• Ability to configure the timestamp format of the build output folder

Note: It it highly recommended to update to the latest DBB 2.0 PTF UI83593 / PH51222. For all available fixes, checkout the IBM DBB Support page.

What's Changed

• Leverage MQ file flag by @dennis-behm in #245
• Search path configuration updates by @dennis-behm in #267
• ZunitConfig.groovy updates by @dennis-behm in #299
• Remove zunit_resolutionRules from required build properties by @dennis-behm in #307
• Externalize the Build Folder Timestamp Format by @donnellt in #314
• Synchronising git history because of cherry picked commits by @dennis-behm in #324
• Updating zappbuild test framework by @dennis-behm in #325
• Simplify obtaining the playbackDependency by @dennis-behm in #311
• Implement language configuration strategy to provide alternative approach to define overrides by @Anuprakash-Moothedath in #295
• Fixed lib imports and deployType in REXX.groovy by @M-DLB in #320

New Contributors

• @Anuprakash-Moothedath made their first contribution in #295
• @donnellt made their first contribution in #314

Full Changelog: 3.0.1...3.1.0

zAppBuild v3.0.1

This is a maintenance release which is including minor corrections and updates.

What's Changed

• Readability of command examples by @ijmitch in #249
• Stop updating output collection when build state in error (zAppBuild 3.0 stream) by @dennis-behm in #261
• Updated zAppBuild test framework by @dennis-behm in #240
• Update required DBB Toolkit version by @dennis-behm in #265
• Updating implementation to create MetadataStore connection by @dennis-behm in #271
• Release zAppBuild 3.0.1 by @dennis-behm in #300

Full Changelog: 3.0.0...3.0.1

zAppBuild v3.0.0

New & Noteworthy

zAppBuild v3.0.0 has been upgraded to support the new DBB 2.0 Metadata Store APIs that provide direct access to Db2 databases used to store DBB build metadata directly from the DBB Toolkit running on z/OS UNIX without requiring a Liberty Web Application.

IMPORTANT! zAppBuild 3.0.0 requires DBB 2.0 toolkit and is not backward compatible with earlier versions of DBB. Customer's still using earlier versions of DBB can check out the zAppBuild_2_x which will be used to continue to provide maintenance for zAppBuild 2.x.

Please also see IBM Docs for details on the new API.

Full Changelog: 2.5.2...3.0.0

zAppBuild v2.5.2

This release is a small release to merge develop into main before the major zAppBuild v3.0.0 release.

What's Changed

• Fix NPE when using dependency file (#230)
• Assembler.groovy removal of hard coded library name (#237)
• Skip unnecessary impact calculation on created full build list (#236)
• Revised implementation of reporting of external impacts feature (#239)

Full Changelog: 2.5.1...2.5.2

zAppBuild v2.5.1

This is a fix release to zAppBuild v2.5.0 when using a dependency files in user builds.

Details on the dependency files can be found at samples/userBuildDependencyFile/README.md

What's Changed

• Fix NPE when using dependency file (#230) by @drbruce-git in #231

Full Changelog: 2.5.0...2.5.1

zAppBuild v2.5.0

New & Noteworthy

This release of zAppBuild allows to move from the DepedencyResolver and ImpactResolver APIs to the new SearchPathDependencyResolver and new SearchPathImpactFinder APIs which got introduced with IBM Dependency Based Build 1.1.2 .

While the old APIs of the IBM Dependency Based Build toolkit are marked as deprecated, these new APIs allow to specify wildcards in the Search Path configuration and can also include the file extension to be able to more precisely define how dependencies and impacts are resolved. Please be aware, that this requires an update to the configurations in application-conf/application.properties. This release of zAppBuild retains backward compatibility with older DBB Toolkit versions.

Please also see IBM Docs for details on the new API.

New Features

• Ability to switch to the new SearchPathDependencyResolver and new SearchPathImpactFinder APIs
• New CLI option to pass in an property overwrite via a parameter
• Managing file-level properties in individual property files which are stored in the repository

What's Changed

• Update README.md by @GeraldMit in #204
• Leverage new SearchPathDependencyResolver and SearchPathImpactFinder API by @dennis-behm in #201
• update build-conf/README.md (Closes #208) by @BeckerFrank in #210
• fix md syntax to correctly display build log in collapsed section by @dennis-behm in #206
• Update impact resolution rule samples for static linkage scenarios by @dennis-behm in #215
• New CLI option to set or overwrite build property by @dennis-behm in #213
• Update zUnit Config script to support Groovy 4.0 runtime by @dennis-behm in #219
• Mark build as failed on git errors by @dennis-behm in #203
• Replace usage of evaluate with string parsing by @dennis-behm in #217
• Correction PSBgen script by @dennis-behm in #226
• Correction PLI alternate library configuration by @dennis-behm in #224
• Correction REXX error feedback allocation by @dennis-behm in #225
• Ability to manage member level build properties in specific prop files by @dennis-behm in #216
• Correction when loading individual file properties by @dennis-behm in #228
• Release zAppBuild 2.5.0 by @dennis-behm in #220

New Contributors

• @GeraldMit made their first contribution in #204
• @BeckerFrank made their first contribution in #210

Full Changelog: 2.4.0...2.5.0

zAppBuild v2.4.0

Important notes

This zAppBuild release ships the necessary modifications to support the Groovy 4.0.0 runtime which is shipped with IBM Dependency Based Build 1.1.3. Backward compatibility with older DBB toolkit versions is preserved.

If you are on an older version of zAppBuild or maintain your own implementation and are about to upgrade to IBM Dependency Based Build 1.1.3, please review the required changes in PR #182 to enable your version to support the Groovy 4.0.0 runtime and check out the IBM TechNote IBM Dependency Based Build runs with Groovy 4.0.0.

New Features

• Capture file deletions and deleted outputs in DBB build report (requires DBB toolkit 1.1.3)
• Reporting capability to document concurrent changes in other branches

What's Changed

• Correction of additional dependency datasets in SYSLIB for language scripts ASM and REXX by @dennis-behm in #177
• Add import statements for Groovy 4.0.0 compatibility by @lburgess07 in #182
• Formatted console output for impactResolver config only on verbose logging by @dennis-behm in #180
• Add hidden files in subdirectories to excludeFileList by @dennis-behm in #185
• SSI info conditional via a build property for Assembler and BMS language scripts by @dennis-behm in #183
• Enable SSI Info for load modules in fullBuild scenario by @dennis-behm in #187
• Add support for additional repo layout scenario for calculating the directory offset by @dennis-behm in #190
• fix logging for physicalDependencies in verbose mode by @dennis-behm in #192
• Updated description of build properties to store SSI by @dennis-behm in #188
• corrected spelling of linkEditSyslibConcatenation by @flpet-ibm in #195
• corrected spelling of MVSExec object in REXX.groovy by @dennis-behm in #197
• Capture file deletions and deleted outputs in DBB build report by @dennis-behm in #193
• report and validate concurrent changes by @dennis-behm in #166
• Conditionally load BuildReportUtilities by @dennis-behm in #198
• Release zAppBuild 2.4.0 by @dennis-behm in #199

Full Changelog: 2.3.1...2.4.0

zAppBuild v2.3.1

What's Changed

• Correction of additional dependency datasets in SYSLIB for language scripts ASM and REXX by @dennis-behm in #177
• Release zAppBuild 2.3.1 by @dennis-behm in #178

Full Changelog: 2.3.0...2.3.1