-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[ci] Make Kafka integration test more self-siufficient #4982
Labels
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
Comments
yurishkuro
added
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
good first issue
Good for beginners
labels
Dec 1, 2023
Hey @yurishkuro, I've made some improvements to the Kafka integration test script. Now, you can start Kafka from within the script using the
Changes in ci_kafka.yml
Let me know if any further adjustments are needed. Thanks! |
Looks good, please create a pull request |
4 tasks
@yurishkuro I've raised a PR. |
4 tasks
yurishkuro
pushed a commit
that referenced
this issue
Dec 4, 2023
## Which problem is this PR solving? Resolves #4982 ## Description of the changes - Introduced a -k parameter to the kafka-integration-test.sh script. - Modified the script to wait for Kafka availability before proceeding. ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [ ] I have added unit tests for the new functionality - [x] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` Signed-off-by: Ripul Handoo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good first issue
Good for beginners
help wanted
Features that maintainers are willing to accept but do not have cycles to implement
The test script
scripts/kafka-integration-test.sh
is currently very simple, it could use some improvements:-k
parameter is passed. This makes it easier to run the test locally. Example of starting Kafka manually in [test]: make Kafka consumer read from the earliest messages #4981.github/workflows/ci-kafka.yml
starts both Kafka and ZK. Is ZK actually needed with the latest versions of Kafka?while true
loop waiting for Kafka to start - if should instead use a loop counter and be time bound, say no more than 3min, with checks every 5sec or soThe text was updated successfully, but these errors were encountered: