Onboarding new maven snapshots publishing to s3 (opensearch-remote-metadata-sdk)

[peterzhuamazon]

Description

Onboarding new maven snapshots publishing to s3 (opensearch-remote-metadata-sdk)

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.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.97%. Comparing base (ae88640) to head (4faf3e1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##               main     #267   +/-   ##
=========================================
  Coverage     84.97%   84.97%           
  Complexity      489      489           
=========================================
  Files            27       27           
  Lines          1737     1737           
  Branches        161      161           
=========================================
  Hits           1476     1476           
  Misses          190      190           
  Partials         71       71           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[opensearch-trigger-bot]

The backport to 2.19 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-remote-metadata-sdk/backport-2.19 2.19
# Navigate to the new working tree
pushd ../.worktrees/opensearch-remote-metadata-sdk/backport-2.19
# Create a new branch
git switch --create backport/backport-267-to-2.19
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e07aa78007567555f7512670185eb4864f1ca7ff
# Push it to GitHub
git push --set-upstream origin backport/backport-267-to-2.19
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/opensearch-remote-metadata-sdk/backport-2.19

Then, create a pull request where the base branch is 2.19 and the compare/head branch is backport/backport-267-to-2.19.

[peterzhuamazon]

• 2.19: [Backport 2.19] Onboarding new maven snapshots publishing to s3 (opensearch-remote-metadata-sdk) #268

[opensearch-trigger-bot]

The backport to 3.2 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-remote-metadata-sdk/backport-3.2 3.2
# Navigate to the new working tree
pushd ../.worktrees/opensearch-remote-metadata-sdk/backport-3.2
# Create a new branch
git switch --create backport/backport-267-to-3.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 e07aa78007567555f7512670185eb4864f1ca7ff
# Push it to GitHub
git push --set-upstream origin backport/backport-267-to-3.2
# Go back to the original working tree
popd
# Delete the working tree
git worktree remove ../.worktrees/opensearch-remote-metadata-sdk/backport-3.2

Then, create a pull request where the base branch is 3.2 and the compare/head branch is backport/backport-267-to-3.2.