Release 0.28

• INCOMPATIBLE-CHANGE
  The legacy syntax for including project versions in distribution recipes, i.e. [ "NAME", "VERSION₁", "VERSION₂", … ], is no longer recognized.

• ENHANCEMENT (#19)
  Variable assignments specified on the commandline using -D NAME=VALUE are now taken into account when resolving project version includes in distribution recipes. That is, a project version include in a distribution recipe like the following

  variables:
    foo-tag: '1.1'
  
  versions:
  - project@v${foo-tag}

  is now affected by a -D foo-tag="1.2" commandline option.

• BUGFIX
  Analysis results for archives are now cached in some cases that should have worked but did not.

• ENHANCEMENT (#16)
  The variable platform-provides can now be used to describe system packages in terms of provided features, thus interfacing with the automatically analyzed or manually declared required features of projects. For example, the following entry could be used to describe the Protocol Buffers C++ Library:

  platform-provides:
  - name: protocol-buffers-cpp-library
    variables:
      extra-provides:
      - nature: cmake
        target: ProtocolBuffers
      platform-requires:
        ubuntu:
          packages:
          - libprotobuf-dev

  A project version requiring cmake:ProtocolBuffers would then automatically gain libprotobuf-dev as a platform requirement.

• ENHANCEMENT
  Printing of error and warning messages has been improved:

  • Error and warning messages are now printed in color if it makes sense in the current context (apparently running interactively, non-dumb terminal)
  • Messages should no longer be printed twice

• BUGFIX
  ssh sub-processes (started by git ) should no longer hang when encountering issues during host key verification.

• ENHANCEMENT (#15)
  When processing information representing a person, names and email address explicitly specified in the name, aliases and identities sections of the corresponding person recipe take precedence over information collected during automatic analysis of project repositories.

• ENHANCEMENT (#11)
  The install-jenkins command now accepts a profile option which can be used to choose among different Jenkins configuration profiles. The following profiles are currently built in:

  • single-user (default): the Jenkins installation will be used by a single user without additional slaves
  • local-docker: the Jenkins installation will use the Docker daemon on the local machine to dynamically create slaves