This PR prepares the environment in such a way that two executions of elastic-package test system -v could be run in parallel.
For that it is required:
[x] Update compose project name used in service deployer adding a random string
[x] Update compose project name used in agent deployer adding a random string
[x] Update integration policy name adding a random string
[x] ~Do not raise error if uninstall package fails in the tear down~
2024/05/17 16:16:49 ERROR Failed to uninstall package is there any other execution in parallel?: there was an apply error: can't remove the package: could not remove package; API status code = 400; response body = {"statusCode":400,"error":"Bad Request","message":"Unable to remove package with existing package policy(s) in use by agent(s)"}
Reverted this change in favor of installing/uninstalling package as a first/last step of all the test executions.
[x] Update service hostnames used in test config, some options:
~Allow to inject variables in system test configuration files, at least service hostname~.
[x] Modify compose scenarios
[x] Use placeholders for hostname in test package oracle {{Hostname}}
Require to update test packages (oracle)
[x] Fix tests system flags
For a follow up PRs:
[ ] Build directory used for all routines needs to be revisited
2024/05/17 11:58:05 ERROR error running package system tests: could not complete test run: can't install the package: there was an apply error: failed to build package: clearing package contents failed: removing directory failed (path: /home/user/Coding/work/elastic-package/build/packages/nginx/999.999.999): unlinkat /home/user/Coding/work/elastic-package/build/packages/nginx/999.999.999: directory not empty
[ ] Show in each log as a context at least the data stream tested
These steps would allow also to be able to trigger parallel tests directly from elastic-package.
Relates https://github.com/elastic/elastic-package/issues/787
This PR prepares the environment in such a way that two executions of
elastic-package test system -v
could be run in parallel.For that it is required:
{{Hostname}}
For a follow up PRs:
These steps would allow also to be able to trigger parallel tests directly from
elastic-package
.