-
Notifications
You must be signed in to change notification settings - Fork 277
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
[Bug]: How can we download the OpenSearch min artifacts for windows #2754
Comments
@peternied You can download the Windows -min artifacts from here. @peterzhuamazon Can you confirm if its updated link? |
Thanks @bbarani it looks like we can get https://artifacts.opensearch.org/snapshots/core/opensearch/2.4.0-SNAPSHOT/opensearch-min-2.4.0-SNAPSHOT-windows-x64-latest.zip can keep us unblocked. I notice this is different than the previous urls we were using prefixed with |
FYI @scrawfor99 ^ |
@peternied unblocked, link available now.
Thanks. |
Can we please keep this open until we have an answer to this question? |
Agreed, I'll reopen. |
Hi @peternied, the snapshots are accessible via artifacts.opensearch.org. However for other components like plugin zips, etc https://ci.opensearch.org/ci/dbc/distribution-build-opensearch was used. |
Thanks @gaiksaya, glad to see this is documented! According to the documentation there are two different ways to get artifacts, Latest Distribution Url vs Min Snapshots. Are these functionality the same, or are there considerations teams should have to use one vs the other? |
The latest distribution url is more towards distribution artifacts like tarballs, zips, manifest where as the Min Snapshots only focuses on min artifact and will always be latest as it gets overridden in each run. I hope this helps. |
Cool, so it seems like for our build processes we should use the latest distribution url. It looks like the windows build isn't being published to that bucket. Can we use this issue to track that we need to update the build process to mirror the linux builds that are being published |
It is already published as part of the bundle build. |
Does that mean there is a modification to the following URL that will get the latest windows build? https://ci.opensearch.org/ci/dbc/distribution-build-opensearch/3.0.0/6234/windows/x64/zip/builds/opensearch/dist/opensearch-min-3.0.0-windows-x64.zip Could you help me figure out what that url is? |
@peternied it should follow the below format but it looks like we don't have successful full distribution build for 3.0 yet but the below URL works for 2.3.1 at this point in time. @peterzhuamazon can you please confirm? |
@scrawfor99 Checkout the most recent comment [1] to see how we can get the current windows build url [1] #2754 (comment) |
Issue seems resolved for me, thanks for all the help tracking this down |
Describe the bug
Note; this the windows platform specific security demo script opensearch-project/security#2161
We are trying to setup builds and validation of OpenSearch for the Security Plugin,
./gradlew.bat build
functions on a windows machine, but need the minimum artifact, just like how they are obtained for linux withI assume there would be a pattern that would look something like the following. Is there a url we can use to get these artifacts?
[1] Possible windows artifact pattern https://.ci.opensearch.org/ci/dbc/distribution-build-opensearch/$opensearch_version/latest/_windows/x64/zip/_builds/opensearch/dist/opensearch-min-$opensearch_version-windows-x64.zip
Notes
I Inspected a recent 3.0.0 build, https://build.ci.opensearch.org/job/distribution-build-opensearch/6226/flowGraphTable/ Do not see a step where artifacts are uploaded.
The text was updated successfully, but these errors were encountered: