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

Write blogpost on how to use Analysis feature for load tests #3397

Closed
mowies opened this issue Apr 8, 2024 · 0 comments · Fixed by #3487
Closed

Write blogpost on how to use Analysis feature for load tests #3397

mowies opened this issue Apr 8, 2024 · 0 comments · Fixed by #3487
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@mowies
Copy link
Member

mowies commented Apr 8, 2024

Goal

As a follow up to the original analysis blog post we could have a new one that highlights, how users could implement load tests and quality gates with them.

Details

Write a blog post for the keptn blog that builds on top of the original analysis blog post and uses some interesting load test metrics to show off how users could have quality gates around their load test results.

The use case should be done like the following:

  • use argo workflows to execute load tests (maybe with a keptn task)
  • use argo workflows to execute a keptn analysis
  • have some form quality gate based on load tests that were run before

Notes

How to add a blog post: https://keptn.sh/latest/docs/contribute/docs/blog/

@mowies mowies added documentation Improvements or additions to documentation status: ready-for-refinement Issue is relevant for the next backlog refinment labels Apr 8, 2024
@mowies mowies added help wanted Extra attention is needed and removed status: ready-for-refinement Issue is relevant for the next backlog refinment labels Apr 17, 2024
@bacherfl bacherfl self-assigned this Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants