-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[vscode] allow user custom workspace timeout #16220
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-iqqbot-update-the-vs-code-timeout-16157.2 because the annotations in the pull request description changed |
1b8f7a1
to
36959b4
Compare
started the job as gitpod-build-iqqbot-update-the-vs-code-timeout-16157.4 because the annotations in the pull request description changed |
36959b4
to
9d6592a
Compare
@iQQBot I wonder could we show somehow current timeout in the input? cc @gtsiolis @loujaybee for UX review |
And I think we should be cleaner what timeout it is, i.e. idle or inactivity timeout. |
Agree, can we use "Inactivity Timeout" as the language? That's what we use on the docs workspace lifecycle page. See also related docs issue: |
Question: Does this allow longer than 24h to be set? 🤔 |
/werft run 👍 started the job as gitpod-build-iqqbot-update-the-vs-code-timeout-16157.6 |
9d6592a
to
bcc58a8
Compare
bcc58a8
to
9bd9787
Compare
Description
[vscode] allow user custom workspace timeout
Review should happen in gitpod-io/gitpod-code#2, this PR only update
gitpod-web
extensionRelated Issue(s)
Fixes #16157
How to test
Release Notes
Documentation
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-test
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