Separate encrypted repository plugin integ tests #72959
Conversation
The encrypted repository module supports encryption with existing repository plugins. Currently the integration tests with these plugins pull in all of the plugins into the same test classpath. That can cause problems when the dependencies of those repositories need to differ. This commit splits the tests into separate qa subprojects.
rjernst
added
>test
elasticmachine
added
Team:Distributed
|
Pinging @elastic/es-delivery (Team:Delivery) |
|
Pinging @elastic/es-distributed (Team:Distributed) |
|
|
||
| dependencies { | ||
| internalClusterTestImplementation testArtifact(project(':plugins:repository-azure'), 'internalClusterTest') | ||
| internalClusterTestImplementation testArtifact(project(':x-pack:plugin:repository-encrypted'), 'test') |
There was a problem hiding this comment.
FWIW, in this scenario you can omit the test parameter as this is the default.
There was a problem hiding this comment.
I'll leave it for clarity, but feel free to remove it when I'm not looking
I believe it is necessary. The way we build out all of x-pack in settings.gradle is through recursively finding build.gradle files. Otherwise we wouldn't know qa was supposed to be a subproject. |
Roger that. |
The encrypted repository module supports encryption with existing
repository plugins. Currently the integration tests with these plugins
pull in all of the plugins into the same test classpath. That can cause
problems when the dependencies of those repositories need to differ.
This commit splits the tests into separate qa subprojects.