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

Epic: Automated Self-Hosted Testing #7316

Closed
3 of 4 tasks
corneliusludmann opened this issue Dec 20, 2021 · 3 comments · Fixed by #10365
Closed
3 of 4 tasks

Epic: Automated Self-Hosted Testing #7316

corneliusludmann opened this issue Dec 20, 2021 · 3 comments · Fixed by #10365
Assignees
Labels
team: delivery Issue belongs to the self-hosted team type: epic

Comments

@corneliusludmann
Copy link
Contributor

corneliusludmann commented Dec 20, 2021

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 tested

Context

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

  • We have a werft job that tests the latest self-hosted from main and runs the existing integration tests.
  • Test runs on 4 representative environments (tbc what these are, see below for first draft)
  • Tests for fresh installations as well as updates from the previous version/release.
  • Notifications about failed tests.

Measurement

  • Number of tests run per week.
  • Number of different environments we test on on a nightly basis.

Growth Area

  • Onboarding

Proposed Test Environments

  1. AWS
  2. GKE
  3. AWS - airgapped
  4. AWS - self-signed certs

Milestones

  • Milestone 1 - MVP with a basic werft pipeline to run tests
  • Milestone 2 - Support all cloud providers
  • Milestone 3 - Additional testing dimensions
  • Milestone 4: Unittests for terraform script

Full testing surface area defined here (internal)

@corneliusludmann corneliusludmann added type: epic team: delivery Issue belongs to the self-hosted team labels Dec 20, 2021
@corneliusludmann corneliusludmann changed the title Epic: Automated Self-hosted Testing Epic: Automated Self-Hosted Testing Dec 20, 2021
@stale
Copy link

stale bot commented Mar 25, 2022

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.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Mar 25, 2022
@lucasvaltl lucasvaltl self-assigned this Apr 1, 2022
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Apr 1, 2022
@nandajavarma
Copy link
Contributor

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.

@lucasvaltl
Copy link
Contributor

Closing this as we fulfilled the acceptance criteria - we are running nightly tests on 4 platforms :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team: delivery Issue belongs to the self-hosted team type: epic
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

3 participants