On 06/29/2018 10:59 PM, Dan Mick wrote: > 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). The ceph-build-pull-requests Jenkins job you linked to there just checks to verify all our job yamls are sane using `jenkins-jobs test` when a PR is created. The job that /should have/ updated the Cobertura plugin settings is https://jenkins.ceph.com/job/jenkins-job-builder/966/ which got triggered when the ceph-build PR got merged. It failed because `jenkins-jobs update` tried using some cached yaml which was mangled prior to https://github.com/ceph/ceph-build/pull/1057 getting merged. Instead of forcing JJB to wipe its cache before every job [1], I just rm'ed /home/jenkins-build/.cache/jenkins_jobs on all the slave-* static slaves so this shouldn't happen again. [1] https://github.com/ceph/ceph-build/blob/master/jenkins-job-builder/config/definitions/jjb.yml#L19 > > 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. > -- 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
