Modified workflow to create new direct-query directory for async-query-core and add last commit_id to the metadata file #3648
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…y-core and add last commit_id to the metadata file Signed-off-by: Kai Huang <ahkcs@amazon.com>
ahkcs
requested review from
GumpacG,
LantaoJin,
MaxKsyunz,
Swiddis,
YANG-DB,
Yury-Fridlyand,
acarbonetto,
anirudha,
dai-chen,
derek-ho,
forestmvey,
joshuali925,
kavithacm,
mengweieric,
noCharger,
penghuo,
ps48,
qianheng-aws,
seankao-az and
ykmr1224
as code owners
noCharger
reviewed
May 21, 2025
Signed-off-by: Kai Huang <ahkcs@amazon.com>
Signed-off-by: Kai Huang <105710027+ahkcs@users.noreply.github.com>
Signed-off-by: Kai Huang <ahkcs@amazon.com>
…into feat/workflow_change
noCharger
reviewed
May 22, 2025
| echo "Using commit ID: ${COMMIT_ID}" | ||
| # Extract version information from build.gradle | ||
| - name: Extract version from build.gradle |
There was a problem hiding this comment.
I dont think the current shadow jar building depends on opensearch version, can you double check?
There was a problem hiding this comment.
I think the version is used to name the directory that we upload our jar to
There was a problem hiding this comment.
let's decouple it from opensearch release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This workflow automates the process of building and publishing OpenSearch artifacts to a Maven repository. Specifically, it builds the async-query-core shadow JAR and publishes it to the Sonatype snapshots repository under the org.opensearch.direct-query group ID.
Key Operations
Shadow JAR Building and Processing
Maven Repository Publishing
Employs the standard OpenSearch publish-snapshot.sh script to:
Upload the shadow JAR and associated files
Generate and upload Maven metadata files
Downloads the generated Maven metadata XML file
Adds the commit ID to the metadata for improved traceability
Re-uploads the enhanced metadata file
Also publishes the standard plugin ZIP package using the Gradle task: publishPluginZipPublicationToSnapshotsRepository
Output
The workflow publishes the shadow JAR and all required metadata to: https://aws.oss.sonatype.org/content/repositories/snapshots/org/opensearch/direct-query/{VERSION}-SNAPSHOT/
The published JAR can then be used as a dependency in other projects that need the functionality provided by the async-query-core module.