Hi guys, Buildbot has a new friend, Bee.
I've enriched buildbot so it can trigger weekly build packages, and upload them to Google Code, automatically. Package codename is "bee" because of buildbot's new friend. Bleeing edge jallib. Each sunday, at approx. 6 o'clock, Bee is waking up, update SVN, export all sources, build packages according to TORELEASE file, check all samples compile fine, then upload them to Google Code. Only "jallib-pack" (tested lib/samples + comiler) are created and uploaded. This means: - files aren't JSG validated (so last minute commit with inconsistencies won't block upload process) - if there's an error in TORELEASE (can't find files for instance), upload will fail. It's for testing packaging. (- API html doc is generated automatically) There's only one version of bee packages so each upload overwrite previous (because GC doesn't provide an easy way to delete packages via scripting). The VERSION file contains the full version with date, something like "bee-<compiler_version>-<date>". This version will be helpful in order to know what this is about when users report problems. These bee packages are also here to encourage integration to TORELEASE, including dependencies, as soon as possible. So once you're done on an isssue/task, update TORELEASE (and CHANGELOG) so it's included in next bee packages ! Currently it's being tested. This sunday, there should be an automatic trigger. If success, and if noone raises his hand, I'll post on jallist abuot this. Please welcome Bee :) Cheers, Seb -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
