Changes between Version 1 and Version 2 of Ticket #1554


Ignore:
Timestamp:
Feb 8, 2011 7:43:16 PM (4 years ago)
Author:
guest
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1554 – Description

    v1 v2  
    99So the aim of this project is to get the cabal-install client to record the success or failure of each package built, along with some information about the configuration and to upload those reports to the hackage server. The server would have to store and aggregate the reports and derive useful information about each packages to display on the web pages.
    1010
    11  * [/trac/hackage/ticket/184 hackage ticket #184 - the build reporting feature request in the hackage trac]
     11 * [http://hackage.haskell.org/trac/hackage/ticket/184 ticket #184 - the build reporting feature request in the hackage trac]
    1212
    1313On the server side it turns out that there are many tasks that we might like to offload to trusted or anonymous clients (ie not just `cabal-install`), so we would really like a framework for managing reports. That would probably include a way of defining the schema of each report and versioning them. A simple example of a report might be a http://www.dwheeler.com/sloccount/ `sloccount`] report where a client downloads a package, runs `sloccount` over it and reports the results. The server would add this information to the a package stats page. There are dozens of similar ideas for discovering useful information about packages, from simple things like sloccount to generating docs, running tests and code analysis.