[AUTO] [main] Added bwc version 2.4.2.#5560
[AUTO] [main] Added bwc version 2.4.2.#5560opensearch-trigger-bot[bot] wants to merge 2 commits intomainfrom
Conversation
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
b41a5c6 to
b621228
Compare
|
@dblock seems like changes in |
Signed-off-by: Daniel (dB.) Doubrovkine <dblock@amazon.com>
|
@reta We're doing funky things here on main. See if this is OK? Are those comments useful? |
Gradle Check (Jenkins) Run Completed with:
|
@dblock unfortunately they still are: The issue here is that we (OpenSearch) build our own Apache Lucene snapshots and publish them, I sadly don't know the details how often we do that, but we have not done that in a while, and hence we have pretty old 9.5.0 snapshots without 9.4.2 reference :( |
Gradle Check (Jenkins) Run Completed with:
|
|
Gradle Check (Jenkins) Run Completed with:
|
@reta: Thanks for sharing this. I see
There seems to be lucene snapshot workflow which generates the snapshots but needs aws account creds. @dblock @nknize : Any idea how do we trigger this job ? |
Exactly :( |
|
We shouldn't bump Lucene versions without triggering a snapshot build or updating the versions file with the next release (and updating shas). This should happen in a dedicated PR. I went ahead and triggered the next snapshot build. https://github.com/opensearch-project/OpenSearch/actions/runs/3690669028 |
The publish-snapshots step is failing @nknize |
|
/cc @mch2 can you take a look when you get a chance? |
Seems like flaky behavior with OIDC, I've added the most current GH thumbprint manually and kicked off a run of lucene branch_9_4 - created version
Yep my fault sorry about this, I never pushed the cdk code used. I reused this cdk project from data-prepper to use an s3 bucket as our maven repo. Will move all this cdk config to a folder in core. |
|
Closing this in favour of #5570 |
I've noticed that a new tag 2.4.1 was pushed, and added a bwc version 2.4.2.