Hi, is the version of the plugin the latest 1.2.11? 

I see that if you set "Ignore Running to TRUE" then the report should display all running jobs with the previous result and an asterisk, like : 

hi, yes, we are on latest version

socrates any updates or ideas on what else to try? happy to have a chat

socrates pinging again after another week?  any other suggestions? I see you moved this to be no longer in-progress.

socrates trying to ping you again.  I would be happy to discuss further to understand why my instance isn't behaving as expected.

Hi John, sorry I didn't have the time to check it,

It's a strange issue, I guess it's a 'mix' of configuration settings and somehow it doesn't work? I want to search in code,  hopefully, by the end of this week, I will have an outcome.

Just one question, are you using the UI or a pipeline syntax? 

We are using the jenkins UI to configure the aggregator.

socrates any update?  what 'mix' of config settings are you thinking about.  I am happy to check into something or provide further insight if needed.  Thanks.

socrates another week has gone by.  looking for any feedback here.

Hi, sorry for my late response again, too many things to take care of. 

Is there any chance for the previous results of the jobs that were omitted to be in status aborted? 

There is a case when "Ignore Running is set to true" and the plugin should check the previous status,

but this previous status is aborted and the "Ignore Aborted" is set to true.

Fixed in latest release 1.2.12

No. our previous runs do not have aborted status.  but per your message I will try to upgrade to 1.2.13 thanks

This appears to be working correctly now after the update.  Thanks

socrates any update?

socrates any update here please!?

Hello jvautour , you are seeing 'running' job instead of the previous status with an asterisk, right ? 

can you please share also the rest of the configuration ? I appreciate any help you can provide. 

socrates this is the same as before, many screen shots posted.  You have previously fixed it, or so I thought.  It was working agian until we upgraded to the latest.  Now only shows running again.  

we are using Test Results Aggregator PluginVersion2.1 , and as before Ignore Running is set to True

John, compare with previous run is set to true but you want to get the previous result when a job is running, that is the issue now, I will see what I can do 

socrates , no. from screen shot compare to previous is clearly set to FALSE.  I just want to report previous results if job is currently running, as it did before and seems to be broken again with latest release.  

 Ignore running should always compare with the previous no matter the
option compareWithPreviousRun

Hello , yes I meant false, compare with previous in your configuration is set to false but when a job is running you need the previous result. 

I have already a fix prepared, its going to be in the next release as soon as I resolve another issue , thanks