-
Bug
-
Resolution: Fixed
-
Major
-
None
When trying to show CI job results using this plugin we often see the status of Running.
However, we would like to see the previous runs results and noticed the feature of 'Ignore Running Jobs' which has the help text of 'If true then jobs are reported with the previous status and results. Moreover an asterisk at the side of status declares that the job is still running.'
When setting this value to true, the running jobs are simply omitted from the resulting report and email.
Expected: all jobs shown in report with last completed run results shown
Actual:
Ignore Running set to FALSE
Ignore Running set to TRUE
[JENKINS-71019] Ignore Running Jobs does not report previous runs results
John
added a comment - socrates after latest update, we again see 'running' jobs even though correct option is selected to show previous status. please review.
John
added a comment - socrates after latest update, we again see 'running' jobs even though correct option is selected to show previous status. please review. John
added a comment - 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.
John
added a comment - 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
added a comment - 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
John
added a comment - 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.
John
added a comment - 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
This appears to be working correctly now after the update. Thanks