`lifecycles:`

For more information about build lifecycles, see Build lifecycle.

Syntax

lifecycles:
  - lifecycle: string # build lifecycle name that can be invoked from the DBB CLI.
    comment: string # message printed to stdout when the build lifecycle begins executing.
    cli: # command line interface configuration
      usage: string # Used in --help text to describe arguments (non-options)
      options: 
        - option: string # short representation of the option (-opt)
          longOption: string # long representation of the option (--opt)
          hasArg: boolean # true if the option has an argument
          description: string # describes the option
   variables: 
     - name: string # name of variable
       value: string | boolean | number | list | map # value of variable
   tasks: [ task | <taskRef> ] # List of inline task definitions and/or task references.

Properties

`lifecycle`

Lifecycle name. It must be a valid CLI argument string (no quotations required).

`comment`

Text that is printed to the console when the lifecycle starts executing.

`cli`

Additional Command Line Interface (CLI) options and arguments required by the lifecycle.

Example:

    # CLI options specific to userbuild
    cli:
      usage: dbb build user [arguments] [options]
      options:
        - longOption: "dependencyFile"
          hasArg: true
          description: "JSON dependency file provided by an IDE used to skip the execution of the DBB scanner."
        - longOption: "errPrefix"
          hasArg: true
          description: "Error prefix for writing error feedback to the Remote Error List view."
        - longOption: "debug"
          hasArg: false
          description: "Enables the debug options on load modules."

Lifecycle CLI options extend the base zBuilder Command line options and arguments.

`variables`

Optional variables that can be referenced by the task and language configurations used in this build lifecycle.
See variables: for detailed schema.

`tasks`

Ordered list of tasks to execute. These tasks can be references of tasks defined in the global tasks: block or can be inline defined tasks.
See task: for defining task elements.