-
Notifications
You must be signed in to change notification settings - Fork 272
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
[Feature] Publish plugins SNAPSHOT artifacts (along with SNASPHOT distribution) #5096
Comments
We have been pushing the created and we do the same for arm64 @peterzhuamazon @cwperks @reta can we just the leverage this ? :) Thank you |
Thanks @prudhvigodithi . So this is somewhat inconsistent: all these 3 URLs point to the same plugin (at least they should) because the distributions of the plugins do not depend on the OpenSearch packaging. We could leverage that, indeed, but looks more like a workaround, not a solution. |
At the moment we just let every distribution build the native plugins zip, but when release we only release x64/tar version. |
So that we do not need to change the workflow too much. |
Will this address my problem in opensearch-project/opensearch-api-specification#610? I am using the 3.0 docker build and need to install one of the optional plugins. Normal docker reference:
The above example is problematic because (it doesn't work), but I also need to manually match the version to the docker image SHA somehow. |
It will @dblock |
After some talk on the triage meeting I fully understand what @reta is talking about. Similar to: Do a: We can start this with opensearch first, as I just checked we havent done any core snapshot for OSD core on artifacts.opensearch.org for a long time. Thanks. |
Acceptance criteria: |
We also need to add the checksum files alongside the native plugin zips. |
Hi @reta if we put the snapshot native plugins zips on s3, I assume you can directly run |
Thanks @peterzhuamazon, we only need to know the location, if it is different from the released versions fe |
Take a look in the next two days, assuming we should be able to add it as part of min snapshot workflows. |
After offline sync, we will use this folder structure:
|
Hi @reta confirms 2.19.0-SNAPSHOT is up with core plugins 3.0.0-SNAPSHOT still in progress here: https://build.ci.opensearch.org/job/publish-opensearch-min-snapshots/1948/console Thanks. |
Thanks @peterzhuamazon , we have one more issue to clarify, for official plugins we also sign them and publish signature, it seems like we don't do this for snapshots?
|
Yes we dont have signings for snapshots, on both plugins zips and min artifacts. |
Could we do that? I think it will be helpful, or there are any drawbacks? |
The existing min pipeline is not designed to have signing in mind, let me take a look on it today. |
Related OS PR that is pending due to this: |
Is your feature request related to a problem? Please describe
At the moment, we do not publish plugins SNAPSHOT artifacts but min distribution only (see please https://build.ci.opensearch.org/job/publish-opensearch-min-snapshots/). However, it becomes increasingly demanded to have plugins SNAPSHOT artifacts published as well.
Describe the solution you'd like
Publish plugins SNAPSHOT artifacts under S3 bucket
https://artifacts.opensearch.org/snapshots/plugins/
so OpenSearch tooling (opensearch-plugin
, etc) could be used to install them for SNAPSHOT distributions.Describe alternatives you've considered
Publish ZIPs to Apache Maven but that would change completely the distribution model for releases and snapshots.
Additional context
See please opensearch-project/OpenSearch#16219
The text was updated successfully, but these errors were encountered: