Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add library to check, request and assign component release owners #590

Merged
merged 4 commits into from
Mar 6, 2025

Conversation

gaiksaya
Copy link
Member

@gaiksaya gaiksaya commented Mar 4, 2025

Description

This change adds a library to check, request release owners for missing ones and assigns one as well.

Issues Resolved

opensearch-project/opensearch-build#5332

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.

Copy link

codecov bot commented Mar 4, 2025

Codecov Report

Attention: Patch coverage is 81.39535% with 8 lines in your changes missing coverage. Please review.

Project coverage is 83.52%. Comparing base (8f01fa8) to head (9a7b576).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
tests/jenkins/TestComponentRepoData.groovy 72.72% 2 Missing and 4 partials ⚠️
src/jenkins/ComponentRepoData.groovy 90.47% 1 Missing and 1 partial ⚠️
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #590      +/-   ##
============================================
- Coverage     83.62%   83.52%   -0.11%     
- Complexity      142      150       +8     
============================================
  Files           124      126       +2     
  Lines           843      886      +43     
  Branches        100      106       +6     
============================================
+ Hits            705      740      +35     
- Misses           41       44       +3     
- Partials         97      102       +5     

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

if (releaseOwner == null || releaseOwner.isEmpty()) {
componentsMissingReleaseOwners.add(component.name)
if (action != 'check') {
handleMissingReleaseOwner(component, releaseMetricsData, componentRepoData, action)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

notifyMissingReleaseOwner?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It handles both request and assign actions. Hence used the generic name


List<String> maintainersWithTag = componentMaintainers.collect { "@$it" }

switch (action) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the logic to handle different actions?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Its mentioned below. Depending on the request or assign. For requesting it will just comment tagging all the maintainers to volunteer one. If assign it will randomly assign one.


String action = args.action
println("Action is: ${action}")
List<String> validActions = ['check', 'assign', 'request']
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where are we implementing check action here Sayali?
Is it check and assign or check and request based on release time line?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just will just output the the components missing the release owners on the console. What we want to do with it, we can iterate later.

gaiksaya added 4 commits March 6, 2025 14:19
Signed-off-by: Sayali Gaikawad <[email protected]>
Signed-off-by: Sayali Gaikawad <[email protected]>
Signed-off-by: Sayali Gaikawad <[email protected]>
@gaiksaya gaiksaya merged commit dbf78ad into opensearch-project:main Mar 6, 2025
8 of 9 checks passed
@gaiksaya gaiksaya deleted the release-owner branch March 6, 2025 23:28
opensearch-trigger-bot bot pushed a commit that referenced this pull request Mar 6, 2025
Signed-off-by: Sayali Gaikawad <[email protected]>
(cherry picked from commit dbf78ad)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

3 participants