Build marked as failed when multiple builds are in progress

[jamestelfer]

When a build is executing concurrently on different commits, the build is marked as a failure. I believe this is because the code for JobView.lastResult only gets the previous result if the build is running; I think it needs to get the status of the previous completed build instead.

This is related to the improvements from #9 I think, but it's still distinct from them.

I'm sorry I haven't attached a pull request, but I don't have a Java build environment. Thanks for your efforts with this plugin so far.

[jan-molak]

Hi James and thanks for your feedback!
I'll need to look into this one a bit more in depth, since there are several things I need to consider in order to support concurrent builds. For example: how should the progress be represented?
I've got a couple of ideas on how to address the issue you've raised as well as #13 at the same time, so stay tuned :)

Jan

[jamestelfer]

To be honest, while I agree with your thinking, at the moment on my infrastructure the build is often appearing to be broken. Is there any possibility of a quick-fix release, with more thorough functionality coming later?

I realise your time is valuable however, and I can imagine that an interim release might not be worth your time.

Cheers,
JT

[jamestelfer]

Many thanks, Jan, this is greatly appreciated. This is already a great plugin; I'm looking forward to seeing where you go with it.