CritasWang opened a new pull request, #17:
URL: https://github.com/apache/iotdb-client-nodejs/pull/17
## Summary
Extend both e2e workflows to test against **IoTDB 2.0.6 and 2.0.10** via a
version matrix, instead of 2.0.6 only.
- `docker-compose-1c1d.yml` / `docker-compose-1c3d.yml`: image tags are now
parameterized with `${IOTDB_VERSION:-2.0.6}` — local usage is unchanged
(defaults to 2.0.6), CI injects the matrix version.
- `e2e-1c1d.yml` / `e2e-1c3d.yml`: added `strategy.matrix.iotdb-version:
["2.0.6", "2.0.10"]` with `fail-fast: false`, so a failure on one server
version doesn't cancel the other.
- Test-result artifact names now carry the version suffix to avoid upload
collisions between matrix jobs.
## Notes
- The 2.0.10 images changed the default `dn_rpc_address` from `0.0.0.0` to
`127.0.0.1` (this broke the Rust client CI in apache/iotdb-client-rust until
overridden). The compose files here are not affected: they already set
`dn_rpc_address=<service-name>` explicitly on every DataNode.
- `2.0.10` is the latest published `-datanode`/`-confignode` image tag on
Docker Hub at the time of this PR.
## Test plan
- [x] `docker compose config` resolves image tags correctly with and without
`IOTDB_VERSION` set
- [x] Workflow YAML validated
- [ ] CI: all four matrix jobs (1C1D/1C3D × 2.0.6/2.0.10) green on this PR
🤖 Generated with [Claude Code](https://claude.com/claude-code)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
