Skip to content

Release 0.33
Compare
Choose a tag to compare
@scymtym scymtym released this 07 Dec 18:09
· 24 commits to master since this release
release-0.33
3a0b95d

  • Linked against libssl.so.1.1 for Ubuntu Focal (#47)

  • INCOMPATIBLE-CHANGE
    The following Jenkins plugins have been deprecated and seem to no longer be available for download:

    • Warnings
    • Task Scanner
    • Checkstyle
    • PMD

    For this reason, the generator no longer attempts to install the plugins when installing a new Jenkins instance. The "Warnings NG" plugin has
    replaced the above plugins. The generator therefore now generates configuration data for the "Warnings NG" plugin by default. For Jenkins
    instances that have the deprecated plugins installed, the previous generator behavior can be selected by setting the following variables:

    -D aspect.checkstyle.implementation=legacy
-D aspect.pmd.implementation=legacy
-D aspect.tasks.implementation=legacy
-D aspect.warnings.implementation=legacy

  • ENHANCEMENT (#44)
    The variable message can be used to specify a message that should be displayed after processing a project or distribution. The generate command displays all such messages as the final output before terminating the generator process. Example message for a distribution:

    job-list: |
  * ${jobs.list}
message: >-
  Will install your stuff into ${toolkit.dir}.

  Generated the following jobs:

  @{job-list}

  • ENHANCEMENT (#47)
    The !b!include FILENAME and !b!literal-include FILENAME constructs can now refer to the to-be-included file in three ways:

    • FILENAME-NOT-STARTING-WITH-/ is interpreted as a filename relative to the directory of the recipe file in which the include construct occurs.
    • /REST-OF-FILENAME-NOT-STARTING-WITH-/ is interpreted as an absolute filename.
    • //REST-OF-FILENAME is interpreted as a filename relative to the root directory of the repository containing the recipe file in which the include construct occurs, that is REPOSITORY-ROOT/REST-OF-FILENAME.
      So assuming a repository /home/recipes containing a recipe /home/recipes/projects/my-project.project, include filename would be resolved as follows
    !b!include patches/patch.diff            → /home/recipes/projects/patches/patch.diff
!b!include /usr/share/patches/patch.diff → /usr/share/patches/patch.diff
!b!include //patches/patch.diff          → /home/recipes/patches/patch.diff
Assets 3
Loading