-
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
gp rebuild with isolated debug workspace #15795
Conversation
started the job as gitpod-build-ak-rebuild-debug.1 because the annotations in the pull request description changed |
/werft run 👍 started the job as gitpod-build-ak-rebuild-debug.2 |
c6bea97
to
927a56a
Compare
c8142cc
to
95c326f
Compare
1db92b2
to
34cd6d6
Compare
/werft run 👍 started the job as gitpod-build-ak-rebuild-debug.14 |
538b192
to
8ecfb2f
Compare
/werft run recreate-vm=true 👍 started the job as gitpod-build-ak-rebuild-debug.18 |
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-ak-rebuild-debug.19 |
227f746
to
63a9247
Compare
@akosyakov in df00d55, why |
@kylos101 It should apply the same default image which we put in outer loop. it is workspace-full right? |
Good question! I'm not sure, honestly. For example, the outer loop workspace image can be the default To recap, customers can specify their own image in the following ways:
I'm not sure on the use cases for the debug workspace. How useful is the debug workspace, if it doesn't include the customer's intended image/customizations? If it doesn't "need" to use the same workspace image as the outer loop, then |
In this PR we only use |
Thank you for clarifying, @akosyakov ! That helps. 😃 It looks like you're still making changes as of an hour ago, and this is in a draft state, so I'll hold off on approvals for now. |
It's ready. I put hold to actually deploy only on Monday. @iQQBot could you check that we did not overlook something what will break stable features 🙏 Lou wants to start UX testing on Monday after 15 CET. It would be cool to deploy before. /hold |
/werft run 👍 started the job as gitpod-build-ak-rebuild-debug.85 |
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.
LGTM
@@ -239,6 +236,9 @@ func Run(options ...RunOption) { | |||
if cfg.DesktopIDE != nil { | |||
internalPorts = append(internalPorts, desktopIDEPort) | |||
} | |||
if cfg.isDebugWorkspace() { |
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.
do we want to also mark 24999-25003 internal?
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.
Do you mean in the outer container? I don't think so, we don't reserve these ports. They can be used if gp rebuild is not running. If it is running I would prefer to be explicit and maybe provide supervisor api that gp rebuild could add name/description for such ports.
/werft run with-integration-tests=workspace 👍 started the job as gitpod-build-ak-rebuild-debug.87 |
df00d55
to
cea7a83
Compare
/unhold |
Co-authored-by: Pudong Zheng <[email protected]>
cea7a83
to
d6ebdf0
Compare
@csweichel We need a tick from you to land? 🙏 |
Description
This approach creates an isolated debug workspace within the existing workspace using the
docker run
command. To access the debug workspace, a user adds the prefixdebug-
to the original workspace ID and uses the new ID as the debug workspace ID. See [1)] to learn more about the usage.Both the original and debug workspaces share the same workspace, Docker, supervisor, and IDE mounts, but have separate networks. The debug workspace runs an HTTP proxy and SSH server to enable access. The workspace proxy uses the
debug-
prefix to forward traffic to the corresponding workspace.Related Issue(s)
Related to #7671
How to test
gp rebuild
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh