-
Notifications
You must be signed in to change notification settings - Fork 1.4k
[ws-proxy] support ports location for debug workspace #15910
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
|
started the job as gitpod-build-ak-debug-ports.1 because the annotations in the pull request description changed |
| ideServerHost = "localhost:20000" | ||
| workspacePort = uint16(20001) | ||
| supervisorPort = uint16(20002) | ||
| workspaceDebugPort = uint16(20004) | ||
| supervisorDebugPort = uint16(20005) | ||
| debugWorkspaceProxyPort = uint16(20006) | ||
| workspaceHost = fmt.Sprintf("localhost:%d", workspacePort) | ||
| portServeHost = fmt.Sprintf("localhost:%d", workspaces[0].Ports[0].Port) | ||
| blobServeHost = "localhost:20003" |
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.
nits: I prefer net.JoinHostPort to fmt.Sprintf
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.
thanks for the hint, I will remember it 💡
|
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-ak-debug-ports.2 |
Merged by Friday, it will be included in our next deployment. In other words, it will be released from the beginning of next week and will be entirely finished by the end of next week until the traffic shifts. |
|
/hold |
|
before merge, please pass the our integration test 🙏 |
|
started the job as gitpod-build-ak-debug-ports.3 because the annotations in the pull request description changed |
|
@utam0k enabled 👍 I also would like to try but I cannot get working preview envs 😢 |
|
@utam0k I've enabled test for the workspace team. There can I see results? Should be part of build? |
|
I also manually retested for regressions. |
|
/unhold manual and integration tests are passing |
Description
It is a prerequisite to #15795. Based on Pudong's work from #15687.
Related Issue(s)
Fixes #
How to test
It is not possible to test new functionality yet. Only in context of #15795. Review code and tests. Test for regressions, i.e. start a workspace, start something inside and check that you can access it.
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
If enabled this will build
install/previewValid options are
all,workspace,webapp,ide,jetbrains,vscode,ssh