Skip to content

Releases: IBM/dbb-zappbuild

zAppBuild 3.9.0

15 Aug 09:23
f3dfad6
Compare
Choose a tag to compare

New & Noteworthy

This is a rather minor release of zAppBuild. It delivers a new language script via #154 . #516 adds --applicationCurrentBranch to pass in the current application branch for pipeline builds from the CI orchestrator, this skips the computation of the current branch, which can be inaccurate in detached head scenarios.

What's Changed

Full Changelog: 3.8.0...3.9.0

zAppBuild 3.8.0

10 Apr 06:01
a719842
Compare
Choose a tag to compare

New & Noteworthy

The main enhancement with this release is the capability to map build files to language configurations by using the DBB file property syntax as an alternative to the mapping via the languageConfigurationMapping.properties file.

Please read through the below list of changes for the additional delivered changes.

What's Changed

Full Changelog: 3.7.0...3.8.0

zAppBuild 3.7.0

08 Mar 08:36
9f25617
Compare
Choose a tag to compare

New & Noteworthy

The release delivers following enhancements:

  • A new summary of error messages on pipeline builds via #472. Sample output:
***************** Finalization of the build process *****************
...
** Updating build result BuildGroup:MortgageApplication-feature/470-errrorsummary BuildLabel:build.20240213.131754.983
** Build ended at Tue Feb 13 13:18:03 GMT+01:00 2024
** Build State : ERROR
** Total files processed : 5
** Summary of error messages
   *! The build return code (8) for MortgageApplication/bms/epsmort.bms exceeded the maximum return code allowed (0)
   *! The compile return code (12) for MortgageApplication/cobol/epscmort.cbl exceeded the maximum return code allowed (4)
   *! The compile return code (12) for MortgageApplication/cobol/epscsmrt.cbl exceeded the maximum return code allowed (4)
   *! The compile return code (12) for MortgageApplication/cobol/epsmlist.cbl exceeded the maximum return code allowed (4)

and various minor enhancements and fixes.

What's Changed

Full Changelog: 3.6.0...3.7.0

zAppBuild 3.6.0

15 Dec 14:58
dd59b05
Compare
Choose a tag to compare

New & Noteworthy

The release deliverers support for zOS Connect Open API Version 2, improved configuration parameters for IMS programs requiring the IMS language interface module, plus various minor enhancements and fixes.

Starting with this release, the zAppBuild release version is printed to the console to indicate which version you are using. We split the version number in a base version and custom version that allows you to define any modifications of the customised state.

What's Changed

Full Changelog: 3.5.0...3.6.0

zAppBuild 3.5.0

20 Oct 10:29
d177891
Compare
Choose a tag to compare

New & Noteworthy

This release delivers enhancements for Db2 applications that require the DSNEXIT allocated for codepage conversion, updates to the MFS.groovy processing to declare the MFS source as output, ability to use Transfer.groovy to manage binary transfers and lots of smaller enhancements and some bugs fixes.

(Finally) we are shipping a version.properties file that includes a reference to which version of zAppBuild was forked/downloaded from users. This will be updated with future releases.

Please note: This release has addressed a defect when computing the branch name in detached head situation. It now takes the all segments of a branch (e.g. feature/implementSomeCoolFeature). Previously only the last segment was returned to name the DBB Collections and DBB Build Result group. Please assess your installation and be mindful if you used branch names with multiple segments to avoid breaking pipelines.

What's Changed

New Contributors

Full Changelog: 3.4.0...3.5.0

zAppBuild 3.4.0

01 Sep 09:03
d018b5c
Compare
Choose a tag to compare

New & Noteworthy

This release delivers new language scripts: CRB.groovy is processing CICS Resource Builder definitions using the CICS TS Resource Builder to outline how infrastructure as code can be embedded into a build pipeline. The CICS resource definitions for the MortgageApplication are shipped as part of the sample. For z/OS Connect OpenAPI 3.0 artifacts, definitions are located in the same Git repository as the Cobol source code and can be processed with the zCEE3.groovy language script.

The language scripts for Assembler, COBOL and PL/I were enhanced in their link step to leverage the IDENTIFY control statement. This capability from the z/OS Binder allows enriching a load module with information about the source version such as the Git hash.

The management of global, default application and application-level properties was updated to make it easier for build administrators to configure zAppBuild. Please see the new HOWTO.md providing additional guidance on this.
Please note: This release introduces a change for zAppBuild users using the applicationConfRootDir property. This property is replaced with the applicationConfDir setting in build-conf/build.properties.

What's Changed

Full Changelog: 3.3.0...3.4.0

zAppBuild 3.3.0

13 Jul 10:27
9beaa58
Compare
Choose a tag to compare

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

15 May 15:12
85e0df0
Compare
Choose a tag to compare

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

Full Changelog: 3.1.0...3.2.0

zAppBuild v3.1.0

07 Mar 10:38
5a649f0
Compare
Choose a tag to compare

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

New Contributors

Full Changelog: 3.0.1...3.1.0

zAppBuild v3.0.1

16 Dec 08:37
83fbf19
Compare
Choose a tag to compare

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

What's Changed

Full Changelog: 3.0.0...3.0.1