On 7 November 2013 14:05, Didier Roche <[email protected]> wrote: > Le 07/11/2013 15:01, Francis Ginther a écrit : > >> This is separate from coverity, it's code coverage [1] and unit test >> reports [2]. These are some of the few metrics we have to measure our >> test coverage and if we're moving in the right direction. I consider >> it a huge loss if we can't carry this forward. >> >> [1] - http://10.97.0.26:8080/job/mir-trusty-amd64-ci/11/cobertura/? >> [2] - >> http://10.97.0.26:8080/job/mir-trusty-amd64-ci/11/testReport/history/? >> >> Francis > > > Can it be something we dispatch from landing code actually, but more see it > as a service for upstream, that is run, let's say, daily on their trunk and > graphing this somewhere? > > Then, it's up to the manager/component responsible to keep this graph on > track. > Making sense? > Didier
To the general case of needing to instrument the build and extract artifacts off of it, I'm discussing that with Colin in #ubuntu-devel right now. My thought was that we could abuse pkgbinarymangler for this. -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
