Has the "Re-add build to the queue" feature changed recently?
Previously, when we stopped a build (selecting the "Re-add build to the queue" option), the build would go to the end of the queue. This was what we "expected", as our use case for this is generally that there's something more important want to run ASAP that we've already promoted to the head of the queue, but the currently running build is still important to get done sometime.
As of 2019.1.4, the behaviour seems to be to add the running build to the top of the queue, basically just causing it to restart. I'll grant that there's no other way currently that I'm aware of to trigger this behaviour, but we also can't think of a reason we'd want to do this.
Was this an intentional change? If so, could we have an extra option to not re-add to the head of the queue? It's making interrupting existing builds a much more involved process.
Please sign in to leave a comment.
Hi Chris, this seems to be a bug, I was able to reproduce the behaviour.
I've created https://youtrack.jetbrains.com/issue/TW-62669 to fix this.
Sorry for the inconvenience.