-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add tiny load testing script #8310
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
Conversation
Codecov Report
@@ Coverage Diff @@
## main #8310 +/- ##
==========================================
- Coverage 12.31% 11.17% -1.14%
==========================================
Files 20 18 -2
Lines 1161 993 -168
==========================================
- Hits 143 111 -32
+ Misses 1014 880 -134
+ Partials 4 2 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
e4b3601
to
c4f01ea
Compare
c4f01ea
to
fc4614f
Compare
fc4614f
to
cbc8ccc
Compare
/werft run 👍 started the job as gitpod-build-mads-load-test.8 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simple yet effective 🚀
/unhold the queue has been processed, let's see if this auto merges now? |
It won't get merged because a required check is failing (ci/werft/build). The build needs to pass, then tide will merge it. Not sure why prow puts this PR on the queue if a required check is failing :/ /hold |
Good catch @ArthurSens. |
Since this change has nothing to do with preview at all, I assume the failure is due to flakyness. Running a job without preview just to the the green lights ✅ /werft run no-preview 👍 started the job as gitpod-build-mads-load-test.11 |
/unhold |
Description
This introduces a tiny script for running load tests against our VM-based preview environments. It prepares a base branch with an empty commit that contains
/werft with-vm
and then pushes as many branches as you have requested so that Werft will run the build job and thus create a VM and deploy Gitpod to it.The base branch is based off the current branch, that means you can use this to create load tests based on whatever is configured on your branch. E.g. if we wanted to run the load test using a separate VM image than what we have on main then we'd just create a branch where we switch the VM image and then run the load script from that branch.
Related Issue(s)
Fixes https://github.com/gitpod-io/ops/issues/1215
How to test
If you just want to try it out you can use it to trigger a single VM with the following.
I have used this script quite a few times to run small loads tests against Harvester. You can see one analysis of running the script here (internal link).
Release Notes
Documentation
N/A