Monday, June 23, 2008

l10n repackaging - part 5 - introduction



Key concepts for the next weeks

Nightly repackages

Dependent repackages

Release repackages

Bootstrap configuration

Major problems



  1. As a note, SeaMonkey is currently repackaging all it's builds from the "Nightly" machines. It's of course still tinderbox (and I'd be happy to switch over to buildbot one time), but we're doing building and repackaging all in one go, which eases the checkout stuff of course, but probably only works with the smaller number of locales we have.

  2. Kairo, could you explain me or point me out where it is explained how the repackages SeaMonkey works? Is it different from how the firefox repackages work currently?
    Does it download the en-US binaries from
    Oh! I can see that you have l10n repackages along with the en-US, that's nice...

    What is the code that gets run for SeaMonkey repackages? The code same from Tinderbox client?

    The way I prepare a slave to do repackages is to 1) check out with l10n-checkout, 2) make configure, 3) make -c config and 4) a wget of the latest en-US binary. Once ready, I basically check out the code for that specific locale and I "make installers-FOO" inside of browser/locales

    This is a screenshot that shows a little about what I just talked about
    and this is the bug that captures the things I have been trying

  3. I still think that we shouldn't have per-slave setup steps, and that we don't really need them. We should catch up on that on the phone or something.

  4. Pike, as you say I do not like it either and I wish we had this feature in buildbot.
    I will continue the thread on buildbot's mailing list and let's try to arrange another meeting next week

  5. armenzg, SeaMonkey is using plain tinderbox client code currently, the config is up at mozilla/tools/tinderbox-configs/seamonkey/

    Of course, we'll need different solutions when we likely switch over to 1.9.1, where tinderbox clients probably won't work that way.