Skip to content

Releases: exasol/integration-test-docker-environment

New docker-db versions, drop support for docker-db 6.0 and 6.1, bugfixes and one minor improvement

09 Jun 17:04
a66ebf7
Compare
Choose a tag to compare

Summary

This release contains support for new docker-db versions, several bugfixes and a minor improvement which allows a new option for indicating the name server which the docker-db should use. Also, support for legacy Exasol versions (6.0 and 6.1) was removed.

New supported Exasol Versions

  • 6.2: 6.2.14, 6.2.15,
  • 7.0: 7.0.4, 7.0.5, 7.0.6, 7.0.7, 7.0.8, 7.0.9, 7.0.10

If you need further versions, please open an issue.

Tested Docker Runtimes

Bug Fixes:

  • #71: Fix exception if goals are not available for docker builds
  • #26: Exception can get printed multiple times in the final exception summary if a task is the child task of multiple other tasks

Features / Enhancements:

  • #83: Add docker-db versions 7.0.10 and 6.2.15-d1
  • #79: Remove support for Exasol 6.0 and 6.1
  • #72: Add support for new docker-db versions 6.2.14 and 7.0.9
  • #64: Add new docker-db versions
  • #30: Add option for name server and set 8.8.8.8 as default name server

Refactoring:

  • #81: Extract test/utils.py to testing/utils.py
  • #67: Remove DepHell dependency, because it is not maintained anymore

Add support for new Exasol Docker-DB versions, docker runtimes and change packaging to poetry

17 Nov 18:06
0479960
Compare
Choose a tag to compare

In this release, we add support for new Exasol Docker-DB versions and Docker runtimes to the integration-test-docker-environment. For example, you can run the Docker-DB with the NVIDIA Container Runtime to add support for GPUs to the UDFs of the Exasol database. This allows you to test your GPU-accelerated UDFs in your CI environment, before deploying them on your production cluster. Furthermore, we converted the project from a pipenv project to a poetry project to improve packaging and reusability in the future.

New supported Exasol Versions

  • 6.1: 6.1.10, 6.1.11, 6.1.12, 6.1.13
  • 6.2: 6.2.7, 6.2.8, 6.2.9, 6.2.10, 6.2.11
  • 7.0: 7.0.0, 7.0.1, 7.0.2, 7.0.3

If you need further versions, please open an issue.

Tested Docker Runtimes

Bug Fixes:

  • #38: Fix logging of database startup log and fetching all DB logs after startup

Features / Enhancements:

  • #58: Add support for Docker-DB versions 6.1.12, 6.1.13, 6.2.10, 6.2.11, 7.0.2, 7.0.3 and set default to 7.0.3
  • #48: Package with poetry
  • #46: Add support for Exasol Docker-DB 7.0.1
  • #36: Add support for Exasol Docker-DB versions 7.0.0, 6.2.9, 6.2.8, 6.2.7, 6.1.11 and 6.1.10
  • #27: Add support for different docker-runtimes

Refactoring:

  • #28: Refactoring test environment lib code
  • #56: Run all tests for each db version only for master, for pull requests and on request [run all tests] in the commit message
  • #39: Remove print statement or replace them with logging

Integration-Test-Docker-Environment 0.1.0, released 25.06.2020

25 Jun 16:28
18cf321
Compare
Choose a tag to compare

Summary

In this first release we created a docker test environment for Exasol. The test environment consists of two docker containers with their own docker network which isolates them from the host. The first container is an Exasol Docker-DB container and the second container is the test container which can be used for the test execution. The setup script creates a new environment accordingly the given options, creates the Exasol configuration and waits for Exasol database and BucketFS to be available. Afterwards, it runs an initial setup for the database where it uploads the Exasol JDBC Driver and imports some test data.

Currently supported Operating Systems

  • Linux
  • Mac OS X with Intel processors (please consult the README for more details)

Currently supported Exasol Versions

  • 6.0: 6.0.12, 6.0.13, 6.0.16
  • 6.1: 6.1.1, 6.1.6, 6.1.7, 6.1.8, 6.1.9
  • 6.2: 6.2.4, 6.2.0, 6.2.1, 6.2.3, 6.2.5, 6.2.6

If you need further versions, please open an issue.

Features

  • #20: Provide container information on the host and in the test container
  • #19: Cleanup up docker resources after failure during setup
  • #15: Add command line flag to deactivate the database setup
  • #14: Make disk size adjustable
  • #13: Make the DB MemSize adjustable
  • #11: Start the Test-Environment in docker runner to avoid dependency installation