Description
We should create tooling to standardize the building of the JAR used in our stress testing runs. Right now, given stress testing is relatively new nothing in standardized, in some cases the JAR is manually created and in others its simple compilation done in many steps.
Both have issues that they won't react well to changes in what needs to be compiled, for example if the library being stress tested takes a dependency on unreleased code the build will either break or need to be updated to compile the source dependency. We already handle this in CI by having DevOps stages, backed by PowerShell and Python scripts, to determine what code needs to be checked out and what needs to be compiled, we should leverage this in our stress testing builds.
- Create a framework for building stress test JARs.
- Leverage tooling used in CI as this already determines what code needs to be compiled.
- Validate that the framework can handle changes without changing the test JAR build.
- New Maven released dependency is added.
- Additional libraries in the SDK group running stress testing are added.
- Source dependencies on non-SDK group dependencies are added (most common will be azure-core or azure-core-http-netty).