When a student replaces their submission, the running build for it should be aborted
Users that submit some code with endless loops by mistake will probably want to tweak their code and resubmit. If a user has submitted a new solution for their assessment, it doesn't make sense to keep running their old one.
What we could do is perform a quick check to see if the ZipSubmission
that motivated a MavenBuildJob
still exists, every few seconds. If it does not exist anymore, it means it has been replaced by a newer version, and we can kill that build and abort the job immediately
Edited by Antonio Garcia-Dominguez