As a maintainer
I want to run scenario tests with Fabric v3
So that I have confidence that the client API continues to work with Fabric v3
Testing for pull request and merge builds should continue to be run with Fabric v2.5 while it remains a supported LTS release. Prior to release, Fabric v3 testing could be carried out either as a separate build, or using a matrix to test with both Fabric v2.5 and v3. This work could also be deferred until Fabric v3 is released.
Note that no hyperledger/fabric-tools Docker image is published for Fabric v3. This is used in the current scenario tests to run CLI commands when configuring the Fabric network. The scenario tests will need rework to either download and use the CLI commands directly, or to use an alternative approach, such as a Kubernetes operator or fabric-admin-sdk.
As a maintainer
I want to run scenario tests with Fabric v3
So that I have confidence that the client API continues to work with Fabric v3
Testing for pull request and merge builds should continue to be run with Fabric v2.5 while it remains a supported LTS release. Prior to release, Fabric v3 testing could be carried out either as a separate build, or using a matrix to test with both Fabric v2.5 and v3. This work could also be deferred until Fabric v3 is released.
Note that no
hyperledger/fabric-toolsDocker image is published for Fabric v3. This is used in the current scenario tests to run CLI commands when configuring the Fabric network. The scenario tests will need rework to either download and use the CLI commands directly, or to use an alternative approach, such as a Kubernetes operator or fabric-admin-sdk.