7 Commits

Author	SHA1	Message	Date
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
Mikhail f. Shiryaev	a2dc780174	Make backward compatible integration tests runner	2022-04-25 21:16:02 +02:00
alesapin	ba81816dc1	Better cmake	2022-04-20 12:11:55 +02:00
alesapin	0eac4529e0	Preparation	2021-09-06 14:33:39 +03:00
alesapin	31181095e7	Review fixes	2021-05-18 17:08:56 +03:00
alesapin	18bf681a83	Fix pull	2021-05-14 18:35:30 +03:00
alesapin	123715300a	Use keeper in integration tests	2021-05-14 15:30:49 +03:00