opensearch-project / opensearch-project/OpenSearch
[RFC] Automate the addition of group specific label to the created `AUTOCUT` issues
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 13.7k
- Forks
- 3k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 108
Description
Is your feature request related to a problem? Please describe
Today from the metrics framework we have the AUTOCUT issues created from the identified Gradle Check flaky tests. For more information on flaky tests, please refer to the OpenSearch Developer Guide.
Today we have 
Search:Aggregations and Search labels were added later and for some issues the group specific labels are missing.
Describe the solution you'd like
An automation that can take care of adding the group specific labels along with the default labels.
Implementing this automation would reduce the time maintainers spend manually adding group labels and enable specific teams to manage/track their own issues using group labels.
I'm open to discuss some ideas and update the automation to add the group specific labels.
Related component
Build
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with jenkins/gradle/gradle-check-flaky-test-issue-creation.jenkinsfile in opensearch-build, especially the issue-creation flow linked in the report. Trace how default labels are assigned and determine how group-specific labels should be identified. Done means newly created AUTOCUT issues receive the appropriate group labels automatically.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100