Jenkins jobs were failing because of the Cobertura plugin; it seems as though the "thresholds" for marking the build 'unstable' were being automatically set from successful builds, somehow, and then builds were failing to meet that threshold (see https://jenkins.ceph.com/job/ceph-pull-requests/447/ for an example). Jos Collin and I discussed for a while, and decided that the "health-auto-update" and "stability-auto-update" should be reset to False, so Jos pushed https://github.com/ceph/ceph-build/pull/1061 and I merged it, expecting that to also reset the thresholds, so that the plugin could keep running but not fail the builds. However, although the ceph-build PR triggered a job that succeeded, https://jenkins.ceph.com/view/pull-requests/job/ceph-build-pull-requests/1816/, somehow the ceph-pull-requests job didn't get updated (I don't know how). So I've manually set those fields to False in the UI, and reset the thresholds to their previous values. There are two mysteries: 1) why did the ceph-build update not "take" 2) how should the Cobertura plugin really be configured (the documentation is just horrid for that plugin). Hope this is at least an improvement while we resolve the above. -- Dan Mick Red Hat, Inc. Ceph docs: http://ceph.com/docs -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
