1052
Comment:
|
1817
|
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. == Approach == For now, we'll have to live with a split test setup: * Push changes to generate jobs on `staging`. * Copy the jobs over to the `dogfood` database. * Let the `dogfood` build farm generate the templates. |
Line 6: | Line 13: |
== Checklist == | |
Line 12: | Line 20: |
* Being enabled for `staging`. '''TODO: what db-devel revision?''' | * Being enabled for `staging`. '''TODO: what production-configs revision? How will we know it's landed?''' The configuration item in question is `generate_templates` in the `[rosetta]` section. |
Line 16: | Line 26: |
Make sure you have a branch that is pottery-compatible. (We call the code that generates templates from code "pottery"). |
|
Line 26: | Line 38: |
== Procedure == Set up a product series on `staging` and `dogfood`. Set up a pottery-compatible branch on `staging`. |
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.
Approach
For now, we'll have to live with a split test setup:
Push changes to generate jobs on staging.
Copy the jobs over to the dogfood database.
Let the dogfood build farm generate the templates.
Checklist
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?
The configuration item in question is generate_templates in the [rosetta] section.
Suitable branches
Make sure you have a branch that is pottery-compatible. (We call the code that generates templates from code "pottery").
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"
Procedure
Set up a product series on staging and dogfood.
Set up a pottery-compatible branch on staging.