-
Notifications
You must be signed in to change notification settings - Fork 2
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
Publish snapshots to Sonatype Snapshot repository #17
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
name: Publish snapshots to Maven | ||
|
||
on: | ||
workflow_dispatch: | ||
push: | ||
branches: | ||
- 'main' | ||
- '2.*' | ||
|
||
jobs: | ||
build-and-publish-snapshots: | ||
strategy: | ||
fail-fast: false | ||
if: github.repository == 'opensearch-project/opensearch-remote-metadata-sdk' | ||
runs-on: ubuntu-latest | ||
|
||
permissions: | ||
id-token: write | ||
contents: write | ||
|
||
steps: | ||
- uses: actions/setup-java@v4 | ||
with: | ||
distribution: temurin | ||
java-version: 21 | ||
- uses: actions/checkout@v4 | ||
- uses: aws-actions/[email protected] | ||
with: | ||
role-to-assume: ${{ secrets.PUBLISH_SNAPSHOTS_ROLE }} | ||
aws-region: us-east-1 | ||
- name: publish snapshots to maven | ||
run: | | ||
export SONATYPE_USERNAME=$(aws secretsmanager get-secret-value --secret-id maven-snapshots-username --query SecretString --output text) | ||
export SONATYPE_PASSWORD=$(aws secretsmanager get-secret-value --secret-id maven-snapshots-password --query SecretString --output text) | ||
echo "::add-mask::$SONATYPE_USERNAME" | ||
echo "::add-mask::$SONATYPE_PASSWORD" | ||
./gradlew publishMavenJavaPublicationToSnapshotsRepository | ||
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we need to do:
./gradlew publishPluginZipPublicationToSnapshotsRepository
? Refml-commons does the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this is not a plugin. It's a JAR file.
The gradle task is
mavenJava
:opensearch-remote-metadata-sdk/build.gradle
Line 150 in 6c77e4b
ml-commons also publishes a shadow jar in the same line you linked, as does common-utils which we are logically more similar to.
I wouldn't mind having a shadow vs. normal jar discussion and switching to that later if there's a strong reason to, but that's an extra level of complexity right now and I'm really trying to get this published in some way to unblock plugin work. 2.19.0 code freeze is 25 days away so any unnecessary configuration at this point is risking feature delivery.