blob: 08a141a43cf935aa0782d201f4b4ca0deddac9ae (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
The following is a sample page. Data is extracted from the buildd email output via a simple [[BuilddProcmailRecipe]].
Log for successful build of xpdf_1.01-1 (dist=unstable)
Log for failed build of xxdiff_1:2.5-2 (dist=unstable)
Log for failed build of yiyantang_0.7.0-1 (dist=unstable)
Log for successful build of zh-sgmltools_1.1-4.3 (dist=unstable)
Log for failed build of adacgi_1.4-4 (dist=unstable)
Log from sbuild 20020606-1600
Log for successful build of admwebuser_2.1-2 (dist=unstable)
Log for successful build of amaya_5.3-3 (dist=unstable)
Log for failed build of analog_2:5.23-2 (dist=unstable)
Log for failed build of aolserver_3.4.2-1 (dist=unstable)
Log for failed build of cern-httpd_3.0A-3 (dist=unstable)
Log for failed build of chimera2_2.0a19-3.2 (dist=unstable)
Log for successful build of curator_1.3-1 (dist=unstable)
Log for successful build of ezmlm-browse_0.6-2 (dist=unstable)
Log for failed build of galeon_1.2.3-6 (dist=unstable)
Log for successful build of googlizer_0.2-1 (dist=unstable)
Log for failed build of grub-client_0.3.0-3 (dist=unstable)
Log for failed build of hitop_0.35-1 (dist=unstable)
Log for failed build of interchange_4.8.5.20020527-1 (dist=unstable)
Log for failed build of kmago_1.1.2-3 (dist=unstable)
Log for failed build of libapache-csacek_2.1.9-1 (dist=unstable)
Log from sbuild 20020607-0715
Log for failed build of libapache-mod-auth-mysql_3.2-1 (dist=unstable)
Log for failed build of libapache-mod-auth-useragent_1.0-4 (dist=unstable)
Log for failed build of libapache-mod-backhand_1.2.1-1.1 (dist=unstable)
Please use the following space to discuss development of an automated system that accepts buildd email as input and a well-defined status page as output.
-- [[Main/GrantBow]] - 08 Jun 2002
If we ignore TWiki's versioning of this file (or the "well-defined status page") we can have wget downloading a HTML version of the buildd output do some sed magic into a text file and voil�!
Would that be OK?
-- [[Main/JoachimNilsson]] - 08 Jun 2002
Aha, OK, sounds good to me. I'd like to try to get consensus on (at least) which direction to head before proceeding. Then it's the next step to get done the sed magic and building an HTML output from buildd.
-- [[Main/GrantBow]] - 10 Jun 2002
I saw your posts on bug-hurd about this. Adding comments on each package would be a grgeat benefit, but would perhaps require some kind of automatic merging of the comments and new buildd outputs. Which could get messy, even for an avid sed /perl/awk/python/whatever-fu master.
One idea around this could be to decouple the comments from the buildd output. Having a separate Wiki page for each package. Perhaps like this:
Log for failed build of grub-client_0.3.0-3 (dist=unstable) BuilddGrubClientComments
Log for failed build of libapache-mod-auth-mysql_3.2-1 (dist=unstable) BuilddLibApacheModAuthMysqlComments
... or similar. One could even add simple markup to color failed packages red and successful builds green. The biggest issue, however, is the one dealing with commenting buildd results and merging new buildd results with these comments.
-- [[Main/JoachimNilsson]] - 10 Jun 2002
It looks like you need no explicit merging if you just put a [[WikiWord]] for the packge in the end of buildd log line.
But if you meant merging new results with old results I know only two ways:
* Put it all in a hash in memory and update from new log
* Store it in a database and update from the log
For this you need
1. parse buildd log to get date, package name, status
2. either save into database or append to a text file
3. process the updated database/text file
Sounds easy to me. What am I missing?
|
