Onboarding new maven snapshots publishing to s3 (opensearch-java)

[peterzhuamazon]

Description

Onboarding new maven snapshots publishing to s3 (opensearch-java)

Issues Resolved

opensearch-project/opensearch-build#5360

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[reta]

credentials(AwsCredentials::class) {

[peterzhuamazon]

Will try, this is the first time I try this on kotlin. Thanks.

[peterzhuamazon]

* What went wrong:
getenv("MAVEN_SNAPSHOTS_S3_REPO") must not be null

But this will be null until the push commit happens. We should not need to verify this during PR checks.

[reta]

* What went wrong:
getenv("MAVEN_SNAPSHOTS_S3_REPO") must not be null

But this will be null until the push commit happens. We should not need to verify this during PR checks.

I think it is not related to push - the MAVEN_SNAPSHOTS_S3_REPO has to be present in every workflow

[peterzhuamazon]

* What went wrong:
getenv("MAVEN_SNAPSHOTS_S3_REPO") must not be null

But this will be null until the push commit happens. We should not need to verify this during PR checks.

I think it is not related to push - the MAVEN_SNAPSHOTS_S3_REPO has to be present in every workflow

In groovy version of the build.gradle in other plugins, doesnt seem to be a requirement tho.
I can add a default value tho if needed, then override that value during the maven publishing workflow.

[reta]

* What went wrong:
getenv("MAVEN_SNAPSHOTS_S3_REPO") must not be null

But this will be null until the push commit happens. We should not need to verify this during PR checks.

I think it is not related to push - the MAVEN_SNAPSHOTS_S3_REPO has to be present in every workflow

In groovy version of the build.gradle in other plugins, doesnt seem to be a requirement tho.
I can add a default value tho if needed, then override that value during the maven publishing workflow.

Yeah, Kotlin builds are somewhat different, it seems like there are more issues to fix, I could help you later tonight , have to run now, sorry about that

[peterzhuamazon]

https://status.maven.org/incidents/0gpb9c1dxrq7

[opensearch-trigger-bot]

The backport to 2.x failed:

The process '/usr/bin/git' failed with exit code 128

To backport manually, run these commands in your terminal:

# Navigate to the root of your repository
cd $(git rev-parse --show-toplevel)
# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add ../.worktrees/opensearch-java/backport-2.x 2.x
# Navigate to the new working tree
pushd ../.worktrees/opensearch-java/backport-2.x
# Create a new branch
git switch --create backport/backport-1768-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 c064975e26d6cc9192a50289afa83fd43eac0f9e
# Push it to GitHub
git push --set-upstream origin backport/backport-1768-to-2.x
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/opensearch-java/backport-2.x

Then, create a pull request where the base branch is 2.x and the compare/head branch is backport/backport-1768-to-2.x.

[peterzhuamazon]

Running good, thanks!
https://github.com/opensearch-project/opensearch-java/actions/runs/18928665262/job/54040858353