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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to