v8.9.7

What's Changed

• Johnfreeman/issue312 integration test summary by @jcfreeman2 in #316
• JCF: follow through on an idea Eric had for not repeatedly printing t… by @jcfreeman2 in #317

This release improves the output of dbt-build --integtest and dbt-build --unittest.

Full Changelog: v8.9.6...v8.9.7

v8.9.6

What's Changed

• JCF: Issue #314: (further) deprecate dbt-unittest-summary.sh and put … by @jcfreeman2 in #315

This release deprecated dbt-unittest-summary.sh. Its output is now contained in dbt-build --unittest.

Full Changelog: v8.9.5...v8.9.6

v8.9.5

What's Changed

• Johnfreeman/issue302 workarea cloning by @jcfreeman2 in #305
• New scripts renamed to align names with existing dbt actions by @alessandrothea in #306
• JCF: Issue #307: simple change, just have SPACK_DISABLE_LOCAL_CONFIG … by @jcfreeman2 in #308
• JCF: in light of Issue #307, where SPACK_DISABLE_LOCAL_CONFIG is set … by @jcfreeman2 in #309
• JCF: ensure that for bespoke builds (i.e., ones which don't begin wit… by @jcfreeman2 in #310
• JCF: fix the bug described in Issue #311 and allow an "all" option to… by @jcfreeman2 in #313

The primary addition to this release is the availability of dbt-info pymodule all, which will list information on all DUNE-DAQ python packages in the local environment.

Full Changelog: v8.9.3...v8.9.5

v8.9.4

What's Changed

• Johnfreeman/issue302 workarea cloning by @jcfreeman2 in #305
• New scripts renamed to align names with existing dbt actions by @alessandrothea in #306
• JCF: Issue #307: simple change, just have SPACK_DISABLE_LOCAL_CONFIG … by @jcfreeman2 in #308
• JCF: in light of Issue #307, where SPACK_DISABLE_LOCAL_CONFIG is set … by @jcfreeman2 in #309

This release adds functionality for dbt workarea cloning, as well as some minor changes to how local Spack configuration is handled. The latter should not be noticeable or negatively impact users.

Full Changelog: v8.9.3...v8.9.4

v8.9.3

What's Changed

• JCF: add specific commit info for DUNE DAQ Python packages and base i… by @jcfreeman2 in #304

This release adds information about python package hashes to be obtained by running dbt-info pymodule <package> after setting up a release area. For example,

$ dbt-info pymodule drunc
> DUNE DAQ Python package "drunc" taken from commit or branch "d9ca975"

Full Changelog: v8.9.2...v8.9.3

v8.9.2

What's Changed

• Johnfreeman/rename frozen to stable by @jcfreeman2 in #300

Full Changelog: v8.9.1...v8.9.2

v8.9.1

Full Changelog: v8.9.0...v8.9.1

This release changes the name of the --pytest option to --integtest.

v8.9.0

What's Changed

• JCF: DUNE-DAQ/daq-release#426 : update dbt-build to not assume that ninja is on /cvmfs by @jcfreeman2 in #297
• Implement --pytest option to dbt-build by @andrewmogan in #298

Full Changelog: v8.8.0...v8.9.0

The primary update in this release is that, similar to dbt-build --unittest, one can now run dbt-build --pytest to run pytests found in a package's integtest/ directory.

v8.8.0

What's Changed

• Johnfreeman/issue289 code coverage by @jcfreeman2 in #296
  • dbt-lcov.sh will now check the unit test coverage of your locally checked out repositories.
• Separate build and run environments using dev variant by @andrewmogan in #294
  • dbt-setup-release will no longer pull in development tools, namely cmake, gdb, and ninja.
• JCF: on Alessandro's request, add commit hash for each repo to the ou… by @jcfreeman2 in #293
  • dbt-info sourcecode will now display a commit hash for each locally checked out repository.

Full Changelog: v8.7.2...v8.8.0