-
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
Workspace Timeout improvements (JetBrains) #16267
Conversation
started the job as gitpod-build-filiptronicek-jetbrains-plugin-16107.2 because the annotations in the pull request description changed |
/werft run 👍 started the job as gitpod-build-filiptronicek-jetbrains-plugin-16107.7 |
/werft run recreate-vm 👍 started the job as gitpod-build-filiptronicek-jetbrains-plugin-16107.8 |
/hold because 74ccaea needs to be reverted before merging (but kept for testing) |
a876068
to
408f64b
Compare
17838fc
to
74ccaea
Compare
/werft run recreate-vm 👍 started the job as gitpod-build-filiptronicek-jetbrains-plugin-16107.15 |
/werft run recreate-vm 👍 started the job as gitpod-build-filiptronicek-jetbrains-plugin-16107.16 |
9e74a0c
to
aef6c9d
Compare
UX-wise I believe picking from a few options (e.g. 1h, 3h, 12h, 24h) instead of a text field would be simpler. I can't imagine the need to be very specific here, it's usually just "make sure it doesn't suspend". cc @loujaybee |
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
e169148
to
bd1fdec
Compare
This looks like it also closes: Is that correct? |
...nd-plugin/src/main/kotlin/io/gitpod/jetbrains/remote/actions/ExtendWorkspaceTimeoutAction.kt
Outdated
Show resolved
Hide resolved
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.
Cool ! Great job, @filiptronicek
I'm thinking potentially along the lines of use cases:
|
faff1a4
to
c2aabf0
Compare
Co-authored-by: Lou Bichard <[email protected]>
1. Only allow decimal values in timeouts This allowed users to have durations in other number systems like hexadecimal. For example `0xfd` was a valid timeout. 2. Remove "d" (day) as a unit Because this unit is both rejected by the backend and timeouts cannot be longer than 24 hours, it does not make sense to allow it. Co-authored-by: Lou Bichard <[email protected]>
…reted display duration This means that 1439m doesn't become "1439 minutes", but rather "29 hours and 59 minutes"
c2aabf0
to
0e33ca6
Compare
/unhold |
PR progress
Description
This PR adds 5 workspace timeout-related features:
a dialog in JetBrains IDEs so that one can make the workspace timeout anything they desire
humanReadableDuration
as a parameter ofSetWorkspaceTimeoutResult
, so that clients can echo the server-interpreted time duration of the timeout extension.a hard limit of 24 hours for timeouts
better timeout validation: durations like
2H
or20M
are now allowed, while values like0xfd
have been excludeda prettier time output when setting a timeout with
gp timeout set
Related Issue(s)
Following #15815
Fixes #16107
How to test
Gitpod: Extend Workspace Timeout
Release Notes
Documentation
This most likely will require updating the docs
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