Better build announcement script, anyone?

[Reinier Heeres]

Hi all,

I recently started working on a new build announcer script in python. 
It's available at dev.laptop.org/~rwh/announcer.

It parses the build.log to figure out which packages are in a build, and 
then tries to get all the changelogs. For this it looks in 
/home/*/public_rpms/ for ChangeLog files and tries to get changelogs for 
rpms directly from koji (this is probably the biggest advantage compared 
to Bert's script). It also reports changes for versions that have not 
been released. All changelogs and package lists are cached locally. I 
haven't included size deltas yet, but plan to do that within a few days; 
probably the size of the jffs2 or ext3 image will do, and that's easy to 
get.

As an added bonus, it should be possible to create a diff between *any* 
two versions.

It might have been better to integrate it in the actual build process, 
but I think parsing of the changelogs would probably still be the 
trickiest thing. If someone thinks we should integrate it better, my 
code is available and I can help out.

I'd like to compare the output of my script and the present announcer 
for a couple of days to make sure it's an improvement. Then we could 
consider switching.

Here's the mail I got about build 1521 as an example of the rpm ChangeLogs:

Changes in build 1521 from build 1520
-sugar-datastore 0.7.2-2.olpc2
+sugar-datastore 0.7.3-1.olpc2
--- Changes for sugar-datastore 0.7.3-1.olpc2 from 0.7.2-2.olpc2 ---
  *  #5707: Delete files for external properties when an entry is deleted.
  *  #5744: Don't copy files out from usb sticks, do a symlink instead.

Cheers,
Reinier

Bert Freudenberg wrote:
> On Jan 4, 2008, at 4:40 , Chris Ball wrote:
>   
>> I'd like it if we could either prefer ChangeLog entries to RPM
>> changelog entries, or print both in the build changelog.  What
>> do others think?
>>     
>
>
> ... and ...
>
> On Jan 3, 2008, at 7:41 , Bernardo Innocenti wrote:
>   
>> The diff script only got the latest changelog entry and
>> missed those for interim revisions 8, 9 and 10.
>>     
>
>
> ... and ...
>
> On Jan 3, 2008, at 1:08 , Bernardo Innocenti wrote:
>   
>> how about adding the size delta to the build report?
>> So we see how much bloat we're taking incrementally.
>>     
>
> ... and all these requests are valid, but my script is really too  
> dumb for that. It was only meant as an interim solution until proper  
> announcements where sent out by the build process.
>
> So - could anyone write a new script? I don't think mine is fixable,  
> it already does way more than originally intended.
>
> You can see it on dev.laptop.org at ~bert/public_html/updatelogs.sh  
> (cron runs it every 15 minutes). It scrapes build logs by http,  
> generates the html logs at http://dev.laptop.org/~bert/joyride- 
> pkgs.html and sends out mail for any new builds encountered.
>
> - Bert -
>
>
> _______________________________________________
> Devel mailing list
> Devel at lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
>
>