Remove build queue length warning on build list page

[agjohnson]

This piece of UI was never updated to fit somewhere more cohesive in the UI and
I feel is a strange thing to expose directly to users. I think a better
application for this is in an eventual status page. A status page is not a
priority atm though.

[ericholscher]

I'm -0 on removing this. I think it's valuable for users who just see their build stuck in a Triggered state. What is the proposed replacement here? Just let users see their builds hang?

[humitos]

Maybe instead of fully removing it, just changing the wording/copy?

I don't think it's really useful to know as a user that there is a queue of 150 tasks.

Also, not sure but, the word Triggered isn't enough to communicate that it was "launched but not started yet"?

[ericholscher]

Yea, I think something along the lines of "We're experiencing an issue that might cause builds to be delayed" or something would be better than just removing this and having users have no knowledge that things are backed up, but will process.

[agjohnson]

It was originally added when we had frequent build back ups. We don't have this problem anymore so this has turned into more of a liability and poor UI. It shows most commonly on the .com, where exposing queue depth is a bad idea. Currently, I just want this feature gone because of this. I think a better UI/UX is to show an alert state on each hanging build in the build list and on the build detail page if build.state == triggered and build.date > 5m ago. We don't need to hit redis at all for this.

[ericholscher]

Cool. I guess we can worry about it again if we start getting a lot of queue backups. At least the build objects are created now, as opposed to the old days where it was just sending builds into the abyss :)

[agjohnson]

And the hanging build objects are finally shown as terminated too! I think a lot of users assumed their builds were destroying our systems as they sat there.

I'll create an issue for updating the build list.