-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build Test Plugins Stage Failure Job #12 #34
Comments
Hi. After searching file.
Jenkins unable to download snapshot for es 7.4.2. This leads to plugin functional test failed.
|
In order to fix this issue, we can download Opensearch into S3 buckets. Each time when we want to run functional test, download Opensearch from S3 then running it in the backend. |
For 7.7 they use storage.googleapis.com as data source for es snapshot downloading. Can we modify the 7.4 data source to use storage.googleapis.com url as well ? Jenkins log: |
I have use the same approach in our dev infra. However, the only difference is that I have uploaded the artifact to a S3 bucket of the bfs aws account, in order to avoid any complications. This means that Tengda needs to change the download path and credential ID for internal AES infra account. Here is the sample code
And here is the test run. Please ignore the error on ./elasticsearch calls, since the test case is designed to run inside a docker container, the mount path is incorrect in my test code. However, having elasticsearch artifact downloaded and unzipped should be fine for our operation. Please let me know if you need anything else or encounter any issues. Thanks. https://jenkins.bfs.sichend.people.aws.dev/job/Kibana/job/bfs6.5.4_test/20/console |
Script in 'Build Test Plugins' Stage can't find the called file:
node scripts/build_kibana_platform_plugins
Cause :
The elastic team has been making packages out of code within kibana to improve deployment. The package/files this script utilizes 'kbn-optimizer' is in v7.7.1 however it is not present in v7.4.2.
Possible Solutions - Next Steps :
Look through elastic's github repo for issues and PRs that reference these packages/files to guide the debugging process.
The text was updated successfully, but these errors were encountered: