Package: Build Release

This module creates a release archive of the current version of a packages in a client. The archive can be installed with the module pm.Install in any client

Designation

Name

pm.Build

Aliases

Build, pm.PackageBuild

Configuration

Optionen

Package (package)

Name of the package

Package Release File (zip-file)

Absolute path to the Package release file

Directory containing documentation (docu-dir)

The content of the given directory will be added to the package as documentation

Release Type (release-type)

the option can be used to set the version number for the new release automatically based on the rules of semantic versioningMögliche Werte: Major (major), Minor (minor), Fix (fix), Configuration (config), Undefined (undefined)

Custom Metadata Entries (custom-metadata-entries)

A list of additional metadata entries which will be added to the metadata variable of the package. Each entry of the list consists of the key and a value separated by an equal sign

Description

The archive created is in ZIP format and contains three components that are divided into subdirectories.

• config: This directory contains all configuration variables in CSV format
• runtime : The directory contains all runtime variables as empty files
• objects : The directory contains all exported objects in XML format

The config directory may contain subdirectories. If a package contains configuration variables for clients or environments, these are created in subdirectories. The directories are named according to the name of the b4A connection or the environment name. Example:

If a package contains the object PCK.BEST4AUTOMIC_BASE.VARA.DATA$$$B4A-1, then the variable is a client configuration for the b4A connection B4A-1. The object is saved in the package archive under the name config/B4A-1/PCK.BEST4AUTOMIC_BASE.VARA.DATA.

The same procedure is used for objects whose extension is the name of an environment. The environments correspond to the servers- definitions in the configuration. If there is the following entry in defaults.conf, the object PCK.BEST4AUTOMIC_BASE.VARA.DATA$$$TEST is identified as the environment configuration.

server-TEST = ....

Examples

Simple construction of a package release

./b4A pm.Build -C DEV-0001 --package B4A.BASE --zip-file B4A.BASE-1.0.0.zip

Building a package release with previously added custom metadata entries

./b4A pm.Buid -C DEV-0001 --package B4A.BASE --zip-file B4A.BASE-1.0.0.zip --custom-metadata-entries "Key1=value1,Key2=value 2"