-
Notifications
You must be signed in to change notification settings - Fork 0
LOGC-40: Migrate to workbench ClickHouse for tests #72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
- Update services to the latest versions - Add clickhouse.image - Enable access_logging feature
Workbench uses workbench_cluster.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files
@@ Coverage Diff @@
## main #72 +/- ##
=======================================
Coverage 73.19% 73.19%
=======================================
Files 21 21
Lines 1608 1608
=======================================
Hits 1177 1177
Misses 346 346
Partials 85 85
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
30ce72a to
8e432b9
Compare
.github/workflows/tests.yaml
Outdated
| version: v2.1.6 | ||
|
|
||
| - name: Start Workbench | ||
| uses: scality/workbench@improvement/WKBCH-13-clickhouse |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once you'll merge your changes in workbench, just directly make a release, there's no "action" for it and it will directly trigger the necessary workflow.
This prevents "permission denied" errors when go test tries to scan workbench-created directories.
c5a9b8d to
c9febb5
Compare
- Run linter before workbench to avoid permission errors on env/ - Wait for workbench setup container and both ClickHouse shards (port 9002)
c9febb5 to
c2733cc
Compare
Migrates log-courier from using a local docker-compose to deploy ClickHouse to using workbench
Best reviewed commit-by-commit.