-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Epic: Automated Self-Hosted Testing #7316
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Based on the discussion I had with @corneliusludmann, I have made a very rough note on notion, about things we discussed during the chat and a small plan on where to start. |
Closing this as we fulfilled the acceptance criteria - we are running nightly tests on 4 platforms :) |
Summary
Set up werft jobs that automatically install and test (running the existing integration tests) Gitpod self-hosted from
main
on 4 representative infrastructure environments every night as well as manually on demand. Also the update path should be testedContext
Before we can publish a new Gitpod self-hosted release, we need to test the installation on all supported platforms. Doing these by hand is annoying, error-prone, and time-consuming. That's why we need to automate this. This will build our confidence in our releases, which in turn will increase trust with users and customers.
Value
Regular, automated tests ensure more reliable Gitpod releases, increasing our own confidence and our customer's confidence.
Acceptance Criteria
main
and runs the existing integration tests.Measurement
Growth Area
Proposed Test Environments
Milestones
Full testing surface area defined here (internal)
The text was updated successfully, but these errors were encountered: