opensearch-project / opensearch-project/data-prepper
Add performance metrics to releases and pull requests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 374
- Forks
- 354
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
Add performance metrics to releases and pull requests
Describe the solution you'd like
Create a GitHub actions or automated method of running a suite of performance tests associating the results with specific commits and/or tags.
Describe alternatives you've considered (Optional)
Manually executing performance tests on release.
Additional context
Gatling Performance Test Repo could be used as a starting point.
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 by reviewing the Gatling Performance Test Repo linked in the issue and the repository's existing release and pull-request automation. Define how a performance suite will run automatically and how results will be associated with specific commits or tags and exposed for releases and pull requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd, performance, release, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100