-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[tests] Move workspace integration tests to Github Actions #16872
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
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.
if we merge this PR to main and then iterate on it afterwards lets keep the scripts for werft for the time being until the GHA workflow is tested
PREVIEW_ENV_DEV_SA_KEY: ${{ secrets.GCP_CREDENTIALS }} | ||
PREVIEW_NAME: ${{ needs.configuration.outputs.name }} | ||
run: | | ||
set -euo pipefail |
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.
it might be cleaner to keep this script in a separate bash file, and run that file here. That way we keep e.g. syntax highlighting, bash linting, etc.
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.
Will do in a follow-on PR, or, if I have trouble getting having the tests run general. So, expect another PR. ;)
c10f86c
to
47084ed
Compare
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.
this is a test
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.
It's visible from a workspace, thanks Github extension!
Description
Triggering tests via werft continues to break / is brittle. Let's move to Github Actions, copying from IDE team, but manage Workspace secret via GCP Secrets Manager.
As background, Workspace integration tests last worked as of March 10. They may have been broke here.
Related Issue(s)
Fixes # n/a
How to test
Merge this to main, and then test.
@vulkoingim , is there a better way to test?
@iQQBot how do you iterate with your Github Actions for Gitpod? From a fork?
Release Notes
Documentation
Build Options:
Run the build with werft instead of GHA
Run Leeway with
--dont-test
Publish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh