We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
This is just to track a discussion we had about documenting the load testing, so we don't forget it.
cc @Gundersanne @lavocatt
Image Builder is currently being load tested on a weekly basis with failure thresholds reflecting the SLIs. The load tests happen against stage CRC. An example can be found here: https://gitlab.com/osbuild/ci/image-builder/-/jobs/1541382293.
This is cool! Do you have any documentation describing the process? Why gitlab?
A lot of osbuild's CI runs on gitlab pipelines + aws&openstack runners: https://gitlab.com/osbuild/ci. To access stage we need internal network, and we have that in our CI (since it's IT managed aws), it made sense to run them there as a scheduled pipeline. We should/could add a bit more to the testing readme actually https://github.com/osbuild/image-builder/blob/main/test/README.md.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This is just to track a discussion we had about documenting the load testing, so we don't forget it.
cc @Gundersanne @lavocatt
Current state
Image Builder is currently being load tested on a weekly basis with failure thresholds reflecting the SLIs. The load tests happen against stage CRC. An example can be found here: https://gitlab.com/osbuild/ci/image-builder/-/jobs/1541382293.
Question
This is cool! Do you have any documentation describing the process? Why gitlab?
Answer
A lot of osbuild's CI runs on gitlab pipelines + aws&openstack runners: https://gitlab.com/osbuild/ci. To access stage we need internal network, and we have that in our CI (since it's IT managed aws), it made sense to run them there as a scheduled pipeline.
We should/could add a bit more to the testing readme actually https://github.com/osbuild/image-builder/blob/main/test/README.md.
The text was updated successfully, but these errors were encountered: