chore: Reporting size of the jars in GitHub comments

[jeromevdl]

Issue #, if available: #1102

Description of changes:

Display a report in GitHub comments about jars size. (Ideally would be great to have the history and see if it's growing)

Checklist

• Meet tenets criteria
• Update tests
• Update docs
• PR title follows conventional commit semantics

Breaking change checklist

RFC issue #:

• Migration process documented
• Implement warnings (if it can live side by side)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.57%. Comparing base (6a94862) to head (2dd3222).
⚠️ Report is 613 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #1196      +/-   ##
============================================
- Coverage     78.93%   78.57%   -0.36%     
+ Complexity      651      650       -1     
============================================
  Files            74       74              
  Lines          2506     2506              
  Branches        259      259              
============================================
- Hits           1978     1969       -9     
- Misses          446      455       +9     
  Partials         82       82              

☔ 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.

[github-actions]

💾 Artifacts Size Report

Module	Version	Size (KB)
powertools-core	1.15.0	6.43
powertools-serialization	1.15.0	16.48
powertools-logging	1.15.0	38.26
powertools-tracing	1.15.0	12.61
powertools-sqs	1.15.0	26.51
powertools-metrics	1.15.0	13.82
powertools-parameters	1.15.0	34.76
powertools-validation	1.15.0	24.49
powertools-cloudformation	1.15.0	16.47
powertools-idempotency	1.15.0	43.12

[jeromevdl]

Help: How can we compare with previous versions of each artifact? (ideally from maven central or any other way)

[scottgerring]

Hey @jeromevdl can we be of any help here?
Also thinking out loud - could we lean in on sonarqube and use it to track this over time too ?

[jeromevdl]

@scottgerring Yes, for the moment I report the size of the built artifacts. Ideally I'd like to compare with the current release to see if it grows or not, but not sure how to achieve this...

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[jeromevdl]

My idea for the comparison with previous versions:

• During release, generate a json file containing the artifacts size that we push to S3 (public access allowed on the S3 file).
• Then when there is a PR, we retrieve the json file to be able to compare.

We'll do that when refactoring the release process... We can already merge the report itself.

Ready for review!

[scottgerring]

Can we do this with sonar custom metrics?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[jeromevdl]

Will push that initial version without comparison with previous versions.
Actually it would be great to have a report of the new dependencies added... or a dependency tree or something to see if add weight to the final asset the user will deploy.