Skip to content

Modified workflow to create new direct-query directory for async-query-core and add last commit_id to the metadata file #3648

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

ahkcs
Copy link
Contributor

@ahkcs ahkcs commented May 21, 2025

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.

…y-core and add last commit_id to the metadata file

Signed-off-by: Kai Huang <[email protected]>
echo "Using commit ID: ${COMMIT_ID}"

# Extract version information from build.gradle
- name: Extract version from build.gradle
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I dont think the current shadow jar building depends on opensearch version, can you double check?

Copy link
Contributor Author

@ahkcs ahkcs May 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the version is used to name the directory that we upload our jar to

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's decouple it from opensearch release

Signed-off-by: Kai Huang <[email protected]>
@ahkcs ahkcs requested a review from noCharger May 22, 2025 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants