Separate active jobs from completed jobs #2065
Comments
|
I think this will make the UI confusing. If we fix #1677 I don't believe this will be a problem. A workspace can only have a single running job, so I'm not sure what the other view would even display. |
|
Why can it only have one running job? I'm not sure that's a good thing forever, for instance a workspace that has a Windows VM and a Linux VM in it. You'd want to do that in parallel if possible. Having only one running job doesn't weaken the advantage. It makes it easy to distinguish between "something is happening" and "nothing is happening." It's helpful to be able to see that at a glance. |
|
It's on our provisioners in our current model to provision in parallel. I'm not opposed to the second argument. I'd like to see a mock before we make this happen. |
|
I'd like to avoid baking in serial provisioning for a single workspace. Componentizing templates to be parallelizable will be an adventure, but it's an inevitable one. |
|
@tjcran we shouldn't do this for Community. There are many many many unknowns in regards to this ATM. |
|
Yeah, even if those were all resolved, this can wait. |
|
You have no idea what I had to do to create these mocks. With an active job: With no active jobs: In retrospect the text should say "No active jobs" instead of "Active jobs." Eventually we'll have a count. |
|
Almost but not quite. Maybe it's close enough. |
|
This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity. |
|
Closing this as not planned. |
What is your suggestion?
Separate the Timeline (which should be "History" #2064) into two parts: active jobs and completed/terminated jobs. Basically duplicate the current table, limit one to actively running jobs and move it above Resources and omit actively running jobs from the other but leave it otherwise unchanged. Name the first one something like "Actions in progress" or "Pending actions;" there are a half dozen options that work.
Often this section will be empty and just have a header. This is a feature and good.
An elaboration that would make this better would be to change some of the columns. "Pending actions" doesn't need a status, for instance, while it would benefit from an actively updated duration (right now it just shows "In progress" until it's done). "Status" in the History is more general; "Result" would be more appropriate to something that will either be "Succeeded," "Failed," or "Unknown."
Why do you want this feature?
The timeline commingles past and present in a way that can be confusing even ignoring the issue with "Running" (#1677).
Are there any workarounds to get this functionality today?
n/a
Are you interested in submitting a PR for this?
no
The text was updated successfully, but these errors were encountered: