Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[jaeger-v2] Add HotROD integration test for jaeger-v2 (#6138)
## Which problem is this PR solving? - Resolves #6137 ## Description of the changes - Currently in `.github/workflows/ci-docker-hotrod.yml`, we are only testing internally via `.scripts/build-hotrod-image.sh` for `examples/hotrod/docker-compose.yml` while `examples/hotrod/docker-compose-v2.yml` isnt getting covered - For this, in `.github/workflows/ci-docker-hotrod.yml` we are passing `-b` flag to specify the jaeger binary (`all-in-one` or `jaeger`) ## How was this change tested? - For the flags and normal bash scirpt code i tested it manually in seperate bash file so that atleast ensures the basic code test ## Checklist - [x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md - [x] I have signed all commits - [x] I have added unit tests for the new functionality - [ ] I have run lint and test steps successfully - for `jaeger`: `make lint test` - for `jaeger-ui`: `yarn lint` and `yarn test` --------- Signed-off-by: Saumya Shah <saumyabshah90@gmail.com> Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
- Loading branch information