[Improvement] Disable deploy button during build time

[mornir]

When I see the Netlify build logs from my clients, I see that they triggered multiple builds in a very short time span. For example, one of the websites takes about 2 minutes to build and the logs show something like 12:03, 12:05, 12:07.
I suspect that they click several times (by accident) on the deploy button, which queues up deploy commands.
From my testing, double-clicking the deploy button doesn't trigger two builds. However, after ~10 seconds, it will trigger a new build.

I propose to disable the deploy button right after clicking on it and to enable again at after the build has completed.

What do you think? Have you fellow devs run into a similar issue with clients?

[nemethricsi]

good idea! should we / can we help on this?

When I see the Netlify build logs from my clients, I see that they triggered multiple builds in a very short time span. For example, one of the websites takes about 2 minutes to build and the logs show something like 12:03, 12:05, 12:07.
I suspect that they click several times (by accident) on the deploy button, which queues up deploy commands.
From my testing, double-clicking the deploy button doesn't trigger two builds. However, after ~10 seconds, it will trigger a new build.

I propose to disable the deploy button right after clicking on it and to enable again at after the build has completed.

What do you think? Have you fellow devs run into a similar issue with clients?

[RamZallan]

Bump, this would be really helpful! CC @rexxars

[opexchanger]

I had the same problem just now, the button doesn't seem to indicate clearly that the click worked, so it can end up queuing more than one build.

[sjelfull]

Thanks for suggesting this feature, we will keep it in mind!

The complication today is that we don't poll for updates, since the badge takes care of displaying the deploy state.