happy smoke test

[iQQBot]

Description

We want to improve gitpod to be more reliable, in case someone changes the common path, but does not verify, we want to run a simple smoke test for each successful main build

This test only contains

• start a private repo workspace with image build and stop it.

Related Issue(s)

Part of #16196

How to test

1. go to github action , run this action from this branch
2. make sure the test is pass.

e.g. https://github.com/gitpod-io/gitpod/actions/runs/4253507307

FYI, I change some code for wait image build, and already run integration test for workspace and ide, make sure it don't break anything (some failed are expected)

Release Notes

NONE

Documentation

Build Options:

• /werft with-github-actions
  Experimental feature to run the build with GitHub Actions (and not in Werft).
• leeway-no-cache
  leeway-target=components:all
• /werft no-test
  Run Leeway with --dont-test

Publish Options

• /werft publish-to-npm
• /werft publish-to-jb-marketplace

Installer Options

• with-ee-license
• with-slow-database
• with-dedicated-emulation
• with-ws-manager-mk2
• workspace-feature-flags
  Add desired feature flags to the end of the line above, space separated

Preview Environment Options:

• /werft with-local-preview
  If enabled this will build install/preview
• /werft with-preview
• /werft with-large-vm
• /werft with-gce-vm
  If enabled this will create the environment on GCE infra
• /werft with-integration-tests=all
  Valid options are all, workspace, webapp, ide, jetbrains, vscode, ssh

[werft-gitpod-dev-com]

started the job as gitpod-build-pd-happy-smoke-test.10 because the annotations in the pull request description changed
(with .werft/ from main)

[iQQBot]

/werft run with-integration-tests=all recreate-vm

👍 started the job as gitpod-build-pd-happy-smoke-test.11
(with .werft/ from main)

[iQQBot]

Can we use this one? or do we need to add a new one? cc @mads-hartmann

https://github.com/gitpod-io/gitpod/actions/workflows/preview-env-check-regressions.yml

/hold

[mads-hartmann]

These changes look great! I happy reusing preivew-env-check-regression for this.

One thought for a follow-up PR: This job currently doesn't do anything when it fails. Would you be able to have it write a Slack message to #development-pipline - if it becomes annoying we can always disable the Slack message again ☺️

[iQQBot]

Would you be able to have it write a Slack message to #development-pipline

Could you help me to add this webhook URL to the repo secret? cc @mads-hartmann

[mads-hartmann]

@iQQBot Done 🧡 I named it DEVELOPMENT_PIPELINE_SLACK_WEBHOOK_URL

[werft-gitpod-dev-com]

started the job as gitpod-build-pd-happy-smoke-test.20 because the annotations in the pull request description changed
(with .werft/ from main)

[iQQBot]

/werft run with-preview recreate-vm

👍 started the job as gitpod-build-pd-happy-smoke-test.21
(with .werft/ from main)

[iQQBot]

/unhold