-
Notifications
You must be signed in to change notification settings - Fork 294
[Bug] Support specifying distribution for test scripts #1812
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
Comments
Shouldn't the path just include tar? |
Per #1800 , the structure is Looks like |
Verify that the upload permission doesn't need changes since it is wildcard match. https://github.com/opensearch-project/opensearch-build/blob/main/deployment/lib/identities.ts |
What do you propose @tianleh for full build paths? What does the following become? https://ci.opensearch.org/ci/dbc/Playground/tianleh-test/tianle-opensearch-build-3-22/1.3.0/5/linux/x64/ |
I am proposing the following (inspired by your suggestion): the local structure will look like The full urls will become Then there is no need to change the code logic for integ/bwc test. We just need to pass the new url into test command. We may need to update the artifact uploading logic to upload the |
For this file, if we do not want to make any changes, then the artifact upload logic will upload |
One small issue is that the local structure will look a bit messy since it will have |
Right, so that feels strange, but are the artifacts in builds radically different in the two types of builds? I feel like we need to merge builds and dist into a single pipeline, but that's a different problem. |
I will continue with the proposal in #1812 (comment) We can later continue optimizing the local structure since it is not customer facing. |
We need to add the platform folder in test recorder just like the one in distribution. |
This can be closed now as the --paths param already point to specific build manifest, which has distribution related param and information. Thanks. |
Once #1800 is implemented, the manifest.yml path or url will have a subfolder for distribution. We may need to introduce a distribution parameter to figure out which distribution's yml to use.
E.g The current test command is
./test.sh integ-test manifests/1.3.0/opensearch-dashboards-1.3.0-test.yml -p opensearch=https://ci.opensearch.org/ci/dbc/Playground/tianleh-test/tianle-opensearch-build-3-22/1.3.0/5/linux/x64 opensearch-dashboards=https://ci.opensearch.org/ci/dbc/Playground/tianleh-test/tianleh-osd-build-3-22/1.3.0/7/linux/x64
The current logic is to find manifest under
dist/opensearch/manifest.yml
but there could be different distributionsdist/opensearch/tar/manifest.yml
Thetar
will need to be provided from the test command.The text was updated successfully, but these errors were encountered: