1 Meeting on irc.gimp.org:#build-brigade
   2 Meeting started  November 20 2006 16:00 UTC
   3 Meeting finished November 20 2006 17:00 UTC
   4 
   5 In attendence:
   6 ------------------------------
   7 
   8 Thomas Vander Stichele (thomasvs)
   9 Fernando Herrera (fer)
  10 Juan José Sánchez Penas (juanjo)
  11 José Dapena Paz (dape)
  12 Iago Toral Quiroga (iago)
  13 
  14 Meeting log
  15 -----------------------------
  16 
  17 nov 20 17:00:40 <iago>	hi all
  18 nov 20 17:00:54 <juanjo>	hi
  19 nov 20 17:00:59 <iago>	it is time to start the meeting :)
  20 nov 20 17:01:18 <fer>	hi
  21 nov 20 17:01:23 <iago>	I'll upload the minutes
  22 nov 20 17:01:45 <iago>	to live.gnome.org in cade someone is missing
  23 nov 20 17:01:49 <iago>	and for future reference
  24 nov 20 17:02:05 <dape>	yes
  25 nov 20 17:02:08 <dape>	first thing
  26 nov 20 17:02:16 <dape>	I have to leave in 25-30 minutes
  27 nov 20 17:02:29 <iago>	dape: ok
  28 nov 20 17:02:37 <iago>	then I guess it is better you start
  29 nov 20 17:02:39 <dape>	so I would beg we start with jhbuild+buildbot related things
  30 nov 20 17:03:04 <fer>	do you know if F.Peters is coming?
  31 nov 20 17:03:24 <dape>	no news about that :S
  32 nov 20 17:04:01 <dape>	as some of you know, frederic doesn't agree with using buildbot
  33 nov 20 17:04:43 <dape>	but no news appart from that
  34 nov 20 17:04:58 <fer>	oki
  35 nov 20 17:05:31 <iago>	dape: then let's start with buildbot issues
  36 nov 20 17:05:55 <iago>	can you talk a little about its current state?
  37 nov 20 17:05:58 <dape>	ok
  38 nov 20 17:06:01 <iago>	so people can know...
  39 nov 20 17:06:03 <dape>	yes
  40 nov 20 17:06:15 <dape>	I've integrated jhbuild (with some custom patches) with buildbot
  41 nov 20 17:06:35 <dape>	and now I've got a buildbot that configures itself from jhbuild modulesets
  42 nov 20 17:07:00 <dape>	and made some changes to prevent buildbot getting all resources because of starting one server per gnome module
  43 nov 20 17:07:27 <dape>	and I would like to deploy this with gnome 2.16, and, if possible, gnome 2.17
  44 nov 20 17:07:52 <dape>	thomasvs, what about the foundation machines?
  45 nov 20 17:09:03 <iago>	in the email I sent to the list, there was this URL, with a little demo of that buildbot running to build gtk+
  46 nov 20 17:09:06 <iago>	http://gtktests-buildbot.igalia.com/
  47 nov 20 17:09:27 <dape>	oh ok
  48 nov 20 17:09:40 <dape>	that's because the machine is running for other projects
  49 nov 20 17:09:52 <dape>	and I considered I shouldn't run all gnome moduleset
  50 nov 20 17:10:24 <fer>	dape, did you also extend jhbuild to be able to run tests? 
  51 nov 20 17:10:29 <dape>	anyway, I think Igalia has offered another machine for this, and I can try with it in case we can't get the foundation machines
  52 nov 20 17:10:40 <dape>	fer, yes
  53 nov 20 17:10:50 <fer>	cool
  54 nov 20 17:10:54 <dape>	in fact I implemented a simple patch to add a "pathrun" command
  55 nov 20 17:11:03 <dape>	that enables me to run an arbitrary command in a project path
  56 nov 20 17:11:15 <dape>	then I can run standard make check or whatever I need to do
  57 nov 20 17:11:24 <dape>	this gives me more flexibility
  58 nov 20 17:11:43 <fer>	great, have you seen Xan's graphics of cairo performance over the gtk-theme-torturer?
  59 nov 20 17:11:59 <fer>	http://blogs.gnome.org/xan
  60 nov 20 17:12:24 <dape>	yes
  61 nov 20 17:12:28 <fer>	we could hook that in some way that we can get an xml-ouput of every continous build
  62 nov 20 17:12:41 <fer>	and then plot grapchics comparing arbitrary builds
  63 nov 20 17:12:54 <dape>	any output, with my patch we can decide any bash/scripting magic we want
  64 nov 20 17:13:06 <dape>	in fact, the code coverage reports are generated this way
  65 nov 20 17:13:27 <fer>	great
  66 nov 20 17:13:50 <dape>	we should add the code to generate the reports we want in the scripts at the end of compilation
  67 nov 20 17:13:55 <dape>	currently there are two scripts
  68 nov 20 17:14:09 <dape>	one is make-check.sh, that runs the tests, and clean coverage info
  69 nov 20 17:14:34 <dape>	and other is module-reports.sh, that currently simply generate coverage info from tests logs
  70 nov 20 17:14:42 <dape>	but this script could implement more stuff
  71 nov 20 17:15:45 <iago>	there are a lot of things that can be done, and probably more after we talk to maintainers and they give us feedback
  72 nov 20 17:15:54 <dape>	yes
  73 nov 20 17:15:58 <fer>	how do you integrate that output with the html output?
  74 nov 20 17:16:06 <iago>	but we would need some developer work on buildbot to achieve them
  75 nov 20 17:16:29 <dape>	any report tool should generate html, but they should be case per case
  76 nov 20 17:16:51 <dape>	for example, we can get projects with check getting specific html output, performance tools getting their one, etc
  77 nov 20 17:17:07 <dape>	I wouldn't add more than linking this info in a structured way in a first stage
  78 nov 20 17:17:27 <dape>	then we can begin to think in cumulative information, in order to get stats and time charts
  79 nov 20 17:17:48 <dape>	but first, getting the output is a good task itself
  80 nov 20 17:17:55 <iago>	dape
  81 nov 20 17:18:02 <iago>	can you point out 
  82 nov 20 17:18:11 <iago>	some important
  83 nov 20 17:18:20 <iago>	short-term issues
  84 nov 20 17:18:26 <iago>	regarding buildbot
  85 nov 20 17:18:27 <iago>	?
  86 nov 20 17:18:38 <iago>	I mean, tasks that need to be done in buildbot
  87 nov 20 17:18:41 <dape>	oh ok
  88 nov 20 17:18:56 ---	dmalcolm_away is now known as dmalcolm
  89 nov 20 17:18:56 <dape>	I think that short-mid term tasks should be
  90 nov 20 17:19:24 <dape>	try to make patchs in jhbuild for buildbot go upstream
  91 nov 20 17:19:35 <dape>	as many as possible, in order to make maintenance easier
  92 nov 20 17:20:01 <dape>	of course, deploy the buildbot with all the current gnome moduleset
  93 nov 20 17:20:12 <iago>	mmm...
  94 nov 20 17:20:16 <dape>	2.16 at least, and 2.17 also if we can get hardware for this
  95 nov 20 17:20:40 <iago>	we would need a machine for that
  96 nov 20 17:20:40 <dape>	integrate test results for some projects (I think we can try with the tests you get in gtk)
  97 nov 20 17:21:15 <dape>	and cosmetic tasks: better css's in buildbot, maybe with gnome web look and feel
  98 nov 20 17:21:22 <iago>	wedape: yes
  99 nov 20 17:21:34 <iago>	we need to fix the view
 100 nov 20 17:21:39 <dape>	and the other cosmetic task, adding the new rss feed support that's been sent to buildbot mailing list
 101 nov 20 17:21:42 <fer>	so we need a volunteer for that :)
 102 nov 20 17:21:53 <iago>	I guess thomas already has some expirience with that
 103 nov 20 17:21:58 <fer>	or are you guys good with rss? :)
 104 nov 20 17:22:05 <fer>	css I mean
 105 nov 20 17:22:29 <dape>	mmm I have some ideas, but I'm far from being an expert O:)
 106 nov 20 17:22:32 <juanjo>	maybe we can talk to the gnomeweb people for those design tasks
 107 nov 20 17:22:51 <dape>	yes, and they're preparing the new web design
 108 nov 20 17:23:05 <dape>	maybe there can be some ideas on what should we do to make the view kick the ass
 109 nov 20 17:23:30 <dape>	I would like myself to collaborate in the deployment of the current work
 110 nov 20 17:24:14 <dape>	and I would pray for some help to get jhbuild patches upstream
 111 nov 20 17:24:41 <dape>	the ones I implemented need more work to avoid james henstridge get frightened
 112 nov 20 17:26:55 <iago>	I think making the deployment is important
 113 nov 20 17:27:00 <iago>	as soon as we do it
 114 nov 20 17:27:07 <iago>	as sooner we get feedback
 115 nov 20 17:27:54 <thomasvs>	back, sorry
 116 nov 20 17:28:40 <iago>	thomasvs, do you have expirience with the view of buildbot?
 117 nov 20 17:28:54 <iago>	I mean CSS and so
 118 nov 20 17:29:09 <dape>	I have to leave now
 119 nov 20 17:29:24 <iago>	bye dape!
 120 nov 20 17:29:32 <dape>	iago, I think we can use that new development machine here at igalia for deployment, I could deploy the buildbot scripts there
 121 nov 20 17:29:38 <thomasvs>	iago: a little, but my experience is from older buildbot code
 122 nov 20 17:29:47 <thomasvs>	dape: I could use some info on what exactly I should deploy on these build machines here
 123 nov 20 17:29:59 <thomasvs>	dape: if you have an easy recipe for me I can get those machines started
 124 nov 20 17:30:13 <dape>	oh ok
 125 nov 20 17:30:14 <dape>	mmm
 126 nov 20 17:30:29 <dape>	then we can try to get this working
 127 nov 20 17:30:41 <dape>	:( I have to leave
 128 nov 20 17:30:59 <thomasvs>	dape: fine, just send me a mail about what I can do and I will make some time for it
 129 nov 20 17:31:06 <dape>	ok, iago, thomasvs, I can help thomasvs deploying the buildbot stuff in the foundation machines
 130 nov 20 17:31:24 <iago>	dape: ok, that's fine
 131 nov 20 17:31:25 <dape>	take this into account when you make the meeting conclusions O:)
 132 nov 20 17:31:42 <iago>	dape: sure, I won't forget it ;)
 133 nov 20 17:32:33 <dape>	ok, then I'll go
 134 nov 20 17:33:10 <iago>	thomasvs, regarding the view, the buildbot demo that we set up is quite ugly
 135 nov 20 17:33:24 <iago>	you can take a look at it here:
 136 nov 20 17:33:26 <iago>	http://gtktests-buildbot.igalia.com/
 137 nov 20 17:33:58 <thomasvs>	this is a different view from the waterfall view ?
 138 nov 20 17:34:19 <thomasvs>	this is our waterfall for example: http://build.fluendo.com:8080/
 139 nov 20 17:34:49 <dape>	thomasvs, if you click in any module you get the waterfall for that project
 140 nov 20 17:34:50 <thomasvs>	the one dape set up is with each project as its own master inside one common process right ?
 141 nov 20 17:34:55 <dape>	yes
 142 nov 20 17:35:08 <dape>	(still leaving O:)
 143 nov 20 17:35:20 <thomasvs>	heh
 144 nov 20 17:35:29 <thomasvs>	iago: well, someone needs to decide what would be a "nice" view
 145 nov 20 17:35:33 <thomasvs>	I am no HTML wizard
 146 nov 20 17:35:52 <thomasvs>	there are some ideas that would be simple to do
 147 nov 20 17:35:59 <thomasvs>	like, "idle" should go under the builder name
 148 nov 20 17:36:07 <thomasvs>	and the table should be outlined correctly for it
 149 nov 20 17:36:16 <thomasvs>	since this is a view that I assume dape created, it shouldn't be hard to make it look better
 150 nov 20 17:36:16 <--	dape has quit (arg late!!!)
 151 nov 20 17:37:03 <iago>	thomasvs: yes
 152 nov 20 17:37:21 <iago>	I will talk to dape
 153 nov 20 17:37:38 <iago>	to know the details of the current view
 154 nov 20 17:37:58 <iago>	and I send the conlusions to the list
 155 nov 20 17:38:13 <iago>	so we can talk about it along with him
 156 nov 20 17:38:29 <iago>	cause I don't know what he did to get that view
 157 nov 20 17:39:20 <iago>	I think he was talking about a css
 158 nov 20 17:39:43 <iago>	but I'm not sure if that's enough with the current design of the view 
 159 nov 20 17:40:38 <thomasvs>	no, it probably needs some more splitting into the table
 160 nov 20 17:40:41 <thomasvs>	and after that a css
 161 nov 20 17:41:31 <iago>	ok
 162 nov 20 17:41:41 <iago>	there is another issue
 163 nov 20 17:42:10 <iago>	which is the integration of the tests 
 164 nov 20 17:42:28 <iago>	currently
 165 nov 20 17:42:44 <iago>	there is only a stdout flush
 166 nov 20 17:42:48 <iago>	http://gtktests-buildbot.igalia.com/gtk%2B/gtk%2B-sarge/builds/92/step-gtk%2B%20make-check.sh/0
 167 nov 20 17:43:18 <thomasvs>	what should I see ?
 168 nov 20 17:43:49 <iago>	in that url? you should see the result of a "make check" 
 169 nov 20 17:44:03 <thomasvs>	right, but what shows the problem you talk about ?
 170 nov 20 17:44:06 <iago>	ah
 171 nov 20 17:44:15 <iago>	I think it would be nice
 172 nov 20 17:44:24 <iago>	to know in the waterfall view
 173 nov 20 17:44:31 <iago>	if there are failed tests for a module
 174 nov 20 17:44:42 <thomasvs>	right
 175 nov 20 17:44:42 <iago>	maybe the number of passed/failed tests
 176 nov 20 17:44:45 <thomasvs>	I think we do that for gst
 177 nov 20 17:44:52 <iago>	and probably a better view of all that mess
 178 nov 20 17:44:57 <iago>	ah, interesting
 179 nov 20 17:45:00 <thomasvs>	it's a matter of writing some code for the specific step that checks the output of the tests
 180 nov 20 17:45:09 <iago>	yep, the problem
 181 nov 20 17:45:13 <iago>	in the gnome case
 182 nov 20 17:45:17 <iago>	is that probably
 183 nov 20 17:45:28 <iago>	people use diferent tools for their unit tests
 184 nov 20 17:45:32 <thomasvs>	right
 185 nov 20 17:45:44 <thomasvs>	so the step would need to know how to do this.  but we can push people in the direction of using check
 186 nov 20 17:45:57 <thomasvs>	that's one of the reasons why we chose to standardize on check for gst - so that we could use the same way of parsing the info at the end
 187 nov 20 17:46:17 <thomasvs>	I can't remember if I ended up writing the buildbot step to look at it, and I do not have one deployed that has it it seems
 188 nov 20 17:47:09 <thomasvs>	I did it for flumotion and coverage
 189 nov 20 17:47:11 <thomasvs>	http://build.fluendo.com:8071/
 190 nov 20 17:47:19 <thomasvs>	<-- the orange blocks (some of them at least) show coverage status
 191 nov 20 17:47:48 <thomasvs>	and it parses the output to find the percentage and displays it as part of the waterfall.  we can do this too for gnome, for failed tests and coverage
 192 nov 20 17:47:55 <iago>	I see
 193 nov 20 17:48:09 <iago>	the problem is that some people will not use check :/
 194 nov 20 17:48:19 <iago>	currently I'm trying to convince people in gtk+ to use it
 195 nov 20 17:48:34 <iago>	but seems they prefer doing something from scratch
 196 nov 20 17:48:41 <iago>	to avoid a new dependency
 197 nov 20 17:48:42 <thomasvs>	which I think is silly, but hey
 198 nov 20 17:48:53 <thomasvs>	it's a devel-time dependency, so it shouldn't be an issue
 199 nov 20 17:48:56 <iago>	 :)
 200 nov 20 17:49:11 <thomasvs>	but my plan of attack was to improve the gstreamer use of it and add these things to our buildbots and use the output from it to convince other people
 201 nov 20 17:49:16 <thomasvs>	just haven't had much time to do that
 202 nov 20 17:49:24 <thomasvs>	I want to show graphs over time of coverage data and test result data
 203 nov 20 17:49:27 <thomasvs>	all from our buildbot
 204 nov 20 17:49:45 <iago>	yes, we also added coverage to our demo:
 205 nov 20 17:49:45 <thomasvs>	but it takes work :/
 206 nov 20 17:49:59 <juanjo>	thomasvs, it would be nice to get your opinion in the gtk-list thread, cause Tim Janick is proposing to do something from scratch and it is difficult to go on with check if some of the maintainers are not convinced
 207 nov 20 17:50:06 <iago>	http://gtktests-buildbot.igalia.com/gnomeslave/gtk+/lcov/gtk/index.html
 208 nov 20 17:50:13 <thomasvs>	juanjo: hm, I'm not on that list
 209 nov 20 17:50:38 <thomasvs>	iago: yeah, I have something like that for gst, I think dape used my template to get to that point
 210 nov 20 17:50:51 <thomasvs>	iago: I still need to integrate it to make sure it gets run on every build and then uploaded somewhere though
 211 nov 20 17:50:54 <juanjo>	thomasvs, we can CC you if you want to get into the discussion anyway ;-)
 212 nov 20 17:51:04 <thomasvs>	juanjo: yes, sure
 213 nov 20 17:51:12 <thomasvs>	or subscribe me to the list :)
 214 nov 20 17:52:12 <iago>	thomasvs: I guess we can make the tests run under Check look nice under buildbot
 215 nov 20 17:52:31 <iago>	that would be good point to push maintainers to use check
 216 nov 20 17:52:35 <thomasvs>	iago: yes, exactly
 217 nov 20 17:54:09 <iago>	ok, so I think we talked about all 
 218 nov 20 17:54:12 <iago>	summarizing
 219 nov 20 17:54:26 <iago>	dape and you will work on the buildbot deployment
 220 nov 20 17:55:14 <iago>	I can try to play a little bit with the view
 221 nov 20 17:55:45 <iago>	and meanwhile I'll try to keep unit tests for gtk+ rolling
 222 nov 20 17:56:19 <iago>	thomasvs: btw, I think that your expirience could be valuable in the gtk-devel debate on unit tests
 223 nov 20 17:56:53 <iago>	I'll send you an email
 224 nov 20 17:57:04 <iago>	pointing to the thread in case you cant to participate
 225 nov 20 17:57:11 <thomasvs>	ok
 226 nov 20 17:58:10 <juanjo>	once we have a cool demo working, we could focus in other things like getting the collaboration of maintainers, doing some more marketing about the build brigade work (gnomejournal,etc.), and all the social side of the work... but for now, I think the main goal is to get in a couple of months a cool demo of what can be done
 227 nov 20 17:59:01 <iago>	juanjo: yes, definitely
 228 nov 20 17:59:49 <iago>	ok, so I guess this is all, not bad for a first meeting :)
 229 nov 20 18:00:16 <iago>	I'll upload the minutes to l.g.o and send an email to the list to keep all people informed
 230 nov 20 18:00:17 <juanjo>	should we schedule a meeting every month for tracking the work? 
 231 nov 20 18:00:23 <juanjo>	is this day and hour ok for everyone?
 232 nov 20 18:00:54 <--	Casanova has quit (http://prashblog.com -- One day I am going to find this `peer' and reset his connection)
 233 nov 20 18:01:23 <iago>	juanjo: it is ok for me and dape
 234 nov 20 18:01:28 <iago>	I think it would be nice
 235 nov 20 18:02:44 <juanjo>	btw, i will talk with josh about handling the channel with burrito, in order to be able to keep a topic and gather people interested here :)
 236 nov 20 18:03:14 <iago>	juanjo: yes, good point :)
 237 nov 20 18:05:54 <juanjo>	ok, it seems the meeting is over :) I think we can have the next one by mid-december to see how things are going
 238 nov 20 18:05:57 <thomasvs>	juanjo: mondays in the middle of a working day is very hard for me
 239 nov 20 18:06:08 <thomasvs>	but I will adapt if that's what other people want
 240 nov 20 18:07:12 <juanjo>	thomasvs, would it be better for you to do it later/earlier? 
 241 nov 20 18:07:55 <thomasvs>	juanjo: yeah, I'd prefer outside of work hours.  like for example 20.00 GMT, or 19.00 spanish time
 242 nov 20 18:08:52 <iago>	that time would be ok for me
 243 nov 20 18:09:08 <iago>	I can talk to dape and check if it ok for him too
 244 nov 20 18:09:18 <juanjo>	that would be ok for me too
 245 nov 20 18:11:01 <juanjo>	ok guys, need to leave now, see you later!
 246 nov 20 18:11:05 <--	juanjo has quit (Leaving)
 247 nov 20 18:11:20 <thomasvs>	later!