ClickHouse/docker/test/integration
Igor Nikonov dbfb448290 Fix: integration test, standalone keeper mode
There is logic regarding which keeper binary use to start keeper cluster in an integration test
There 2 options:
(1) standalone keeper binary (expected binary name clickhouse-keeper)
(2) clickhouse binary with keeper inside

Fixed:
- option (1) didn't work since docker_compose_keeper.yaml didn't create
target clickhouse-keeper at all
- if clickhouse-keeper existed, option (1) was taken but
  clickhouse-keeper could be just a link to clickhouse binary (the link
  is created always during build if cmake option BUILD_STANDALONE_KEEPER is OFF)
2022-09-09 14:51:34 +00:00
..
base Change mysql-odbc url 2022-07-29 11:52:20 +02:00
dotnet_client Add test output and compare to reference 2022-01-03 03:36:23 +03:00
helper_container Preparation 2021-09-06 14:33:39 +03:00
hive_server update hive test 2022-06-21 15:10:48 +08:00
kerberized_hadoop Create symlink hadoop -> ./hadoop-2.7.0 2022-02-13 19:10:11 +01:00
kerberos_kdc Fix more tests 2021-09-09 23:29:42 +03:00
mysql_golang_client fixup! Update golang-mysql integration image 2022-04-23 15:24:42 +02:00
mysql_java_client Preparation 2021-09-06 14:33:39 +03:00
mysql_js_client Fix WORKDIR issue after upgrading npm 2022-04-05 00:10:33 +02:00
mysql_php_client Update mysql_php_client php version 2022-04-22 18:22:14 +02:00
postgresql_java_client Preparation 2021-09-06 14:33:39 +03:00
resolver Preparation 2021-09-06 14:33:39 +03:00
runner Fix: integration test, standalone keeper mode 2022-09-09 14:51:34 +00:00
s3_proxy Preparation 2021-09-06 14:33:39 +03:00
README.md

Docker containers for integration tests

  • base container with required packages
  • runner container with that runs integration tests in docker
  • runnner/compose contains docker_compose YaML files that are used in tests

How to run integration tests is described in tests/integration/README.md