Onboarding new maven snapshots publishing to s3 (AD)

[peterzhuamazon]

Description

Onboarding new maven snapshots publishing to s3 (AD)

Related Issues

opensearch-project/opensearch-build#5360

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

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 81.38%. Comparing base (2cbf1f7) to head (be1809b).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1590      +/-   ##
============================================
- Coverage     81.46%   81.38%   -0.09%     
+ Complexity     6136     6129       -7     
============================================
  Files           542      542              
  Lines         24898    24898              
  Branches       2540     2540              
============================================
- Hits          20282    20262      -20     
- Misses         3350     3370      +20     
  Partials       1266     1266              

Flag	Coverage Δ
plugin	81.38% <ø> (-0.09%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 12 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

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

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

[peterzhuamazon]

• 2.19 backport: [Backport 2.19] Onboarding new maven snapshots publishing to s3 (AD) #1592