|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
> Is this still an issue in recent versions of Jenkins?
Yes, absolutely. One could argue that this lies in the very nature of incremental builds and affects everything which calculates a trend (or something similar) from the build results - e.g. also FindBugs/Checkstyle warning trends.
I guess there wouldn't even be a 100% solution possible for this.
For example, if we would like to take the test results from the last build where the skipped module was actually build, we might not have it anymore, as that build may have been
archived awaydeleted, already.