Purge xUnit/jUnit test results which are showing stale information
I've noticed that after you build a job which produces xUnit/jUnit test results, the front matter of the job which shows failures tends to "remember" the first failure in a run. If you then re-ran the test and it generates another error message, that message will NOT show through that front failure section. It DOES get remembered further down if you click through to the very final test result screen. I've also noticed something similar with this testing information - if you remove a build workspace, the xUnit/jUnit trend graph will fail. However if you replace one build number with another (in the filesystem, and reload), the count of passed/failed tests is still remembered from the original build. Where is this information stored? I would like to know how to delete it. I haven't been able to find it on the filesystem. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f20819a4-926e-4bca-bf93-6d2dd5c7c457%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Separating build failure from test failures
I'd like to somehow separate on the Jenkins page the difference between jobs which failed due to a build/script error versus jobs which had failing tests. I use the PowerShell plugin and can set the overall pass/fail based on that - sure. But then I lose visibility on the front page that a job had failing tests within it. Does anyone have a workaround? I saw a plugin a while ago that could add Pass/Fail counts (but not indicators) to the front view. But I don't remember the plugin name and it didn't function with Folders (and it was a view, so, it was nigh impossible to replace the All view, as you know how difficult it can be for folders). Thanks. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3f08873e-838a-4669-be74-3d46f1cc8388%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
CannotResolveClassException: jenkins.metrics.impl.TimeInQueueAction
I recently went through and removed a whole bunch of non-essential plugins. Since then each day I open Jenkins to a new "Manage Old Data" message which are these CannotResolveClassExceptions against every freestyleJob. I discard it, they go away, and it's back the next day. I have Job DSL which generates those jobs, and the jobs are scheduled to run each morning, but there's really nothing special in them. If I run them manually it doesn't generate the message. Would anyone have a clue what might be causing it? I'm on Jenkins 2.37. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/39e80938-5981-41c3-90ea-c720027506e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: DON'T upgrade to Credentials plugin 2.1.7
Unfortunately no, I'm still pretty new and didn't know what to include. I did do due diligence restarting multiple times, replacing old and new plugin and seeing it fail every time on the old one. But later in the day I must have upgraded again and with no ill effects. So apologies for the alarm. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/f2175377-a4b9-4a06-b235-72e4892b6b8c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
DON'T upgrade to Credentials plugin 2.1.7
It killed my Jenkins instance. I had to revert (by removing the .jpi from the plugins directory and renaming the .bak to .jpi). -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e2e72be1-0201-48e9-a9af-c7fc1423a122%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
