Onboard maven publish to 1-click release process

[rishabh6788]

Description

Add publishToMaven method to 1-click release job.
I have set the auto-publishing to false to fist test if everything looks correct.
Once verified will set it to true.

Issues Resolved

opensearch-project/opensearch-build#4592

Is this a backport? If so, please add backport PR # and/or commits #

Testing

[Please provide details of testing done: unit testing, integration testing and manual testing]

Check List

• New functionality includes testing
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented
• Commits are signed per the DCO using --signoff

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.

[rishabh6788]

cc: @gaiksaya Please take a look.

[AndreKurait]

@rishabh6788, Our gradle project is within a sub directory TrafficCapture that I think needs to be specified. See AndreKurait@ebf6b5c

[gaiksaya]

Needs changes on github release drafter as well with right gradle command to bundle the artifact.

Do we still need to publish to artifacts.opensearch.org? Looks like the artifact was never released https://build.ci.opensearch.org/view/Release/job/opensearch-migrations-release/

If yes, in that case we need a mechanism to distinguish what needs to be published on maven and what needs to be published on S3

[AndreKurait]

Yes, we want to start publishing to artifacts as well. Let me know what change needs to be made to the gradle or github if i can help

[rishabh6788]

Needs changes on github release drafter as well with right gradle command to bundle the artifact.

Do we still need to publish to artifacts.opensearch.org? Looks like the artifact was never released https://build.ci.opensearch.org/view/Release/job/opensearch-migrations-release/

If yes, in that case we need a mechanism to distinguish what needs to be published on maven and what needs to be published on S3

@gaiksaya As discussed I have moved the standard release pipeline logic into opensearch-migrations repo jenkinsfile. I have also updated the release-drafter workflow to generate maven jars and upload it to draft release.

Please review the PR carefully and provide feedback.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.54%. Comparing base (5865ca3) to head (44434ae).
Report is 6 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main     #546      +/-   ##
============================================
- Coverage     76.64%   76.54%   -0.10%     
+ Complexity     1414     1408       -6     
============================================
  Files           155      155              
  Lines          6033     6033              
  Branches        543      543              
============================================
- Hits           4624     4618       -6     
- Misses         1044     1049       +5     
- Partials        365      366       +1     

Flag	Coverage Δ
unittests	76.54% <ø> (-0.10%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Comment addressed