[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Peter Winkler commented on JENKINS-25340 lost trend history after skipping build Thanks for the information. I've made an interesting detection. It seems that the complete history trend information is still there. To be found at url-head/jenkins-job-name/lastCompletedBuild/testReport/history/countGraph/png?start=0end=100". (There I can see a history of 100 items although there was gaps in the history due to deleted builds.) For the moment I can put this url in a img-html statement in the job description and have back the old trend graph. That would means that the history graph shown by junit plugin isn't the same as before and it would be enough to change something in the junit plugin only. Is that right? 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.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Peter Winkler commented on JENKINS-25340 lost trend history after skipping build In our opinion the assumption that there is no gap in the number of history builds is a bad assumption. It is comparable with the assumption that the offered feature to delete builds is no longer a valid feature. Besides building our firmware we use JENKINS to test our firmware in several test suites in the hours of the night. In this topic means FAILED (red) that a firmware error avoids the complete test suite, UNSTABLE (yellow) that the suite has found firmware errors and STABLE (green) that the suite passed without finding firmware errors. To keep this meaning we delete test builds on following conditions: Not our firmware raised a FAILED build (e.g. network problems or github server problems) The test build was interrupted due to any reason (test developer want to change versions to be tested, forgotten configuration etc.) For developing purpose (to test the test in the JENKINS environment) only a subset of test cases was started in the suite (because the whole suite would be taken hours) May be there are more reasons to use the “delete build” feature. In formerly JENKINS versions this procedure was possible without influence to the history graph. With the change due to JENKINS-23945 such a delete of a build disturbs the history graph that kind that deletion of builds is out of usability. We hope that there is another possibility to be aware JENKINS-23945 on the one hand and keep the history graph independent of gaps in the build list raised by deletion on the other hand. 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.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Peter Winkler commented on JENKINS-25340 lost trend history after skipping build The suggestion to use “skipping” would only solve a small part of our problems. A problem which leads to a build failure before the first test case is started disturbs the statistics because the firmware to be tested wasn’t responsible for that. Moreover “skipping” is already used for test cases which meet hardware where they have to skip. We couldn’t differentiate these two things. But nevertheless I wonder that a well-established behavior of JENKINS is changed that restrictively kind without unease that the customers could have a problem with that change. I expected at least two things: a configuration item to give the customer the control to switch back to the old behavior a warning in the release notes about the new behavior (anyhow this would have spared the analysis time to find out the really reason of the new behavior, may be I’m wrong, but I haven’t seen such a warning) With respect to the fact that the change in https://github.com/jenkinsci/jenkins/commit/8d8102036f4e52aada39db37c05025b9bb31516d seems more like a work around than a solution of JENKINS-23945 (may be JENKINS-24380 is one) it is questionable whether a lost of a well-established functionality can be accepted. 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.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Peter Winkler commented on JENKINS-25340 lost trend history after skipping build So I've a last two questions: 1. Is there any timeline where it is planned to start with JENKINS-24380? 2. Is it guaranteed that after JENKINS-24380 is fulfilled trend history comes back to old behavior? 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.
