@bufferunderrun, @robin, my 2c:

1. Log scrolling

Instead of a button to enable or disable automatic scrolling, I think it would be better to make a more intuitive UX by doing the following:

1. If the logs are already scrolled down to the bottom, then stick to the bottom.
2. If the user scrolls up, then do not auto scroll.
3. Create an icon button next to the download logs button that allows the user to stick to the bottom of the logs again. This button is only visible if the current logs view is not sticking to the bottom of the logs.

2. Displaying current step name

I like the idea, but we need to make sure it's not displayed on the mobile view.

3. Progress as time spent

current_time_spent / estimated_time_spent

Since this is highly variable behavior, I do not recommend this as a default option.

Perhaps what we could have instead is an icon button that the user can click in order to obtain a live view of the progress. The tooltip for the icon button should say that the estimate is based on the last x number of builds of the same job.

I would also recommend this be displayed as a percentage calculation (where the percentage math is done client-side in the browser). The reason behind this is that it reduces the amount of space taken up. We can still keep the full current_time_spent / estimated_time_spent as a tooltip to the percentage.

Happy to hear your feedback.

Create an icon button next to the download logs button that allows the user to stick to the bottom of the logs again

Icon choice is critical here. The download logs icon already has a down arrow, so I wonder if there's any icon for "scroll to the bottom" that would not be a down arrow-like design, because this would create a bit of ambiguity.

One other thing I forgot to mention for displaying the step name

We could also dynamically update the step name in the title (client-side code only). Currently, the page title has only the build number. Perhaps we could also have the build number and then the step name in the page title.