Diff for "Translations/GenerateTemplatesOnTestServers"

Not logged in - Log In / Register

Differences between revisions 2 and 3
Revision 2 as of 2010-04-20 09:08:38
Size: 1093
Editor: jtv
Comment:
Revision 3 as of 2010-04-20 09:09:46
Size: 1226
Editor: jtv
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Right now we have no good test platform for this: `staging` has no build farm, and `dogfood` has no codehosting. Expect this page to change a lot as we work and learn.
Right now we have no good test platform for this: `staging` has no build farm, and `dogfood` has no codehosting. Expect this page to change a lot as we work and learn.  We already have pages about [[Translations/GenerateTemplatesOnLocalBuildFarm|doing this on a development system]] that may also help.

Trying out template generation on dogfood/staging

Right now we have no good test platform for this: staging has no build farm, and dogfood has no codehosting. Expect this page to change a lot as we work and learn. We already have pages about doing this on a development system that may also help.

Config

Make sure that generating templates is enabled in the Launchpad lazr config.

  • Enabled for dogfood.

  • Enabled on development systems.
  • Being enabled for staging. TODO: what production-configs revision? How will we know it's landed?

Suitable branches

We don't yet know for sure what real-world branches will work right out of the box. We must fix that!

According to wgrant, editing configure.ac to set GETTEXT_PACKAGE ("or something like that") does the trick.

TODO: Easy litmus test to see if a branch will work with pottery.

TODO: Find good real-world sample branch for testing—preferably small but with multiple templates.

Once you have a suitable branch, you can copy it to staging's codehosting using "bzr push -d lp:<branch> lp://staging/<branch> --use-existing-dir"

Translations/GenerateTemplatesOnTestServers (last edited 2020-09-17 12:48:23 by cjwatson)