Hi, I'd like to reopen the historical data subject as this is something I find very useful and I don't think I've seen answer to it.
First, let me give you an example of what I'd like to achieve: Generate a report which lists maven projects and which gives them a mark. The mark would show the "best-behaving" projects. It would a function of the activity and the number of time the project has broken the build. The formula doesn't matter and can be improved (like adding the meantime between build failure and build fixes, etc). What is important is that to achieve this we need historical data of build results. And the question, as always is "where do we store build results". Here's the solution I've thought about and for which I'd like to have your feedback: - use a Maven build listener (as in Ant) which logs project builds and failures in an XML format (BTW, that alone is needed to get a Gump-like dashboard). An alternative is a preGoal/postGoal. - this build listener would store the result in the local repository, under: MAVEN_REPO/<groupId>/buildresults/[...] Where [...] could be for example: <pom.id>-<date+time>.xml so that it conforms to the artifact naming convention. The XML would contain the following information: result of build + date of build start + date of build end. Result could be: "success", "failure" or "prereq". Another variant would be: MAVEN_REPO/<groupId>/historical/buildresults/[...] (this means defining a standard place for all historical dato to be saved) - plugins would read that information and generate an HTML report. As mentioned I can already envision 2 plugins: - one for producing a global project dashboard - another one for classifying projects by "best-behaving" Why do I think build result historical data has to be saved in the repo? Because the build result is a product of the build and as such is an artifact. The repo already has the notion of time (with versions). What do you think? Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
