Skip to content

[self-hosted] werft job to install a nightly Gitpod installation #7433

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.

Sign up for GitHub

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

Jump to bottom
Closed
corneliusludmann opened this issue Jan 4, 2022 · 3 comments
Closed

[self-hosted] werft job to install a nightly Gitpod installation #7433

corneliusludmann opened this issue Jan 4, 2022 · 3 comments
Assignees
@nandajavarma
Labels
meta: stale This issue/PR is stale and will be closed soon team: delivery Issue belongs to the self-hosted team

Comments

@corneliusludmann
Copy link
Contributor

corneliusludmann commented Jan 4, 2022 •
edited
Loading

Create a job that installs a Gitpod self-hosted installation as a nightly job and run the existing integration tests. Send a notification to Slack if the integration tests or the installation fails.

See also
@corneliusludmann corneliusludmann changed the title [self-hosted] werft job to install a nightly Gitpod installation on EKS [self-hosted] werft job to install a nightly Gitpod installation Jan 6, 2022
@corneliusludmann corneliusludmann self-assigned this Jan 6, 2022
@corneliusludmann corneliusludmann moved this from 📓Scheduled to ⚒In Progress in 🚚 Security, Infrastructure, and Delivery Team (SID) Jan 6, 2022
@sagor999 sagor999 added the team: delivery Issue belongs to the self-hosted team label Feb 25, 2022
@nandajavarma
Copy link
Contributor

The current WIP of this task can be found here, done by @corneliusludmann. The next step for us is to try and have a werft phase for this job, along with finding a way to run the integration tests on the created cluster. From here, we can iterate and see what might be the right tools to create the managed clusters.

@corneliusludmann corneliusludmann removed their assignment Apr 13, 2022
@stale
Copy link

stale bot commented Aug 11, 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 Aug 11, 2022
@nandajavarma
Copy link
Contributor

Closing this issue in favor of #10620

Repository owner moved this from ⚒In Progress to ✨Done in 🚚 Security, Infrastructure, and Delivery Team (SID) Sep 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nandajavarma nandajavarma

Labels
meta: stale This issue/PR is stale and will be closed soon team: delivery Issue belongs to the self-hosted team
Projects
No open projects
🚚 Security, Infrastructure, and Delivery Team (SID)
Archived in project
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nandajavarma @sagor999 @corneliusludmann