[DNM] Zombienet sdk native provider#8728
Conversation
I tried to use zombienet-sdk Native provider for polkadot-fellows repo and run it with different polkadot/polkadot-parachain versions: polkadot-fellows/runtimes#676 - it was working. |
|
Hey, using native in our CI is possible but to do it we need: Spawn a bigger runner (or use parity-default / parity-large) Also, we should ensure that all the needed nodes fit on the runner (maybe we can mix native for smoke test and k8s for more complex/biggers ones). |
…ased 12 cores test
| ZOMBIE_PROVIDER=native | ||
| ZOMBIENET_SDK_IMAGE_FOR_NATIVE=docker.io/paritytech/ci-unified:bullseye-1.84.1-2025-01-28-v202502131220 | ||
| ZOMBIENET_SDK_RUNNER_FOR_NATIVE=parity-large | ||
| ZOMBIENET_SDK_IMAGE_FOR_K8S=docker.io/paritytech/zombienet:v1.3.129 | ||
| ZOMBIENET_SDK_RUNNER_FOR_K8S=parity-zombienet | ||
| RUST_LOG=info,zombienet_orchestrator=trace,cumulus_zombienet_sdk_helpers=debug |
There was a problem hiding this comment.
Yes, this file is here
It keeps settings for zombienet-sdk.
This way we can separately configure zombienet and zombienet-sdk
There was a problem hiding this comment.
Ahh oks, but we can merge into one file for the final version of the pr. 👍
There was a problem hiding this comment.
I decided to separate files to have clear distinction between options for zombienet and zombienet-sdk.
Unfortunately we cannot put comments in this file because of the way those files are used to inject options into GH environment.
So if we merge into one we shall make sure variables are named in a descriptive way.
There was a problem hiding this comment.
Yes, we can use ZOMBIENET_SDK prefix in all vars related to sdk (only this one is needed to change ZOMBIE_PROVIDER). RUST_LOG could maintain without change since will not have effect in v1.
|
All GitHub workflows were cancelled due to failure one of the required jobs. |
c8218be to
0f5ffeb
Compare
|
Work continued in #8748 |



This is to test zombienet-sdk CI with native provider