-
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
[supervisor] Provide port Name and Description along with the port status #7012
Conversation
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.0 |
@felladrin I tried to run CI but tests are failing: https://werft.gitpod-dev.com/job/gitpod-build-port-description-3059-fork.0 Try to run them locally. |
@felladrin It would be nice if you change the description to use the PR template. It is important for automation, i.e. reference an associated issue and provide proper CHANGELOG. |
Alright! Now I understand how the tests work; gonna try to fix it now.
Hmm, I created the PR via Gitpod workspace, but I don't remember it suggesting a template. |
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.1 |
Codecov Report
@@ Coverage Diff @@
## main #7012 +/- ##
==========================================
- Coverage 19.04% 5.76% -13.29%
==========================================
Files 2 13 +11
Lines 168 1162 +994
==========================================
+ Hits 32 67 +35
- Misses 134 1094 +960
+ Partials 2 1 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.2 |
Ok, so now a new version It is important that VS Code still can run in the cluster where supervisor does not expose such API, so changes should be done in backward compatible manner. The best way to test it a PR in Gitpod VS Code
If you are blocked in port-description-3059-fork.staging.gitpod-dev.com let me know if will grant you access to this env. |
Thanks for contributing, @felladrin! 🌟 fyi: You'll also need to sign a Contributor License Agreement (CLA) once before merging your first contribution. Looping in @meysholdt to reach out about the CLA. 🏀 |
Hi Victor, I've sent you a CLA via DocuSign, can you please sign it so that we can merge this PR? |
Hi, guys. I've signed the CLA. @akosyakov, following your instructions, I was able to test it on gitpod.io, but I couldn't access port-description-3059-fork.staging.gitpod-dev.com (I'm always getting This site can’t be reached [ERR_CONNECTION_CLOSED]). In any case, I've opened a PR on Gitpod VS Code: gitpod-io/openvscode-server#258 - so we can continue the discussion there. |
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.3 @felladrin prev env was down Could you please squash commits. We try to keep history linear and logical. It is fine to have several commits in PR, but in final state commits should be cleaned up. We usually use several commits only when several logical parts are changed or one PR addresses multiple issues. In this case one commit is enough. |
Ok, squashed. By the way, now I'm able to login the prev environment. But received the "blocked" message when trying to open Gitpod VS Code repo there. |
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.4 |
/lgtm |
LGTM label has been added. Git tree hash: b0b5e13c5ab1eeb6b823e3574319f9a8d5eeb17e
|
@gitpod-io/engineering-meta Could you review it please? 🙏 |
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.5 |
@felladrin If we add |
/lgtm Thx @felladrin ! 🙏 |
LGTM label has been added. Git tree hash: 4351f0003c9f2e8f7f213b69c53d748bfed738ee
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: akosyakov, geropl Associated issue: #3059 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/werft run 👍 started the job as gitpod-build-port-description-3059-fork.6 |
Description
Changes on gitpod-protocol and the supervisor-api to add
name
anddescription
toPortsStatus
message, which carries the values obtained from Gitpod Workspace PortConfig.Related Issue(s)
Fix #3059
How to test
Run
port_test.go
, which has one test for the name attribute and another one for the description.Release Notes