## page was renamed from Translations/BuildTemplatesOnLocalBuildFarm = Translation Templates from Branch = This is an attempt to guide you through a manual test of the nascent mechanism to produce translation templates based on a bzr branch. It still needs lots of work. == Patches == * For debugging, edit {{{lib/lp/buildmaster/manager.py}}} and replace {{{logging.INFO}}} with {{{logging.DEBUG}}}. == Enabling local branch access == {{{ mkdir -p /var/tmp/ppa /var/tmp/bazaar.launchpad.test/static }}} There's a bug somewhere in Windmill that may break access to local branches through http. [[https://bugs.launchpad.net/bugs/534399|This bug is scheduled to be fixed soon]]. To see if this is biting you, look in your Apache error log ({{{/var/log/apache2/error.log}}}) for a traceback ending with something like this (your home directory and the version numbers will vary): {{{ File "/home/me/canonical/lp-sourcedeps/eggs/windmill-1.3beta3_lp_r1440-py2.5.egg/windmill/dep/_mozrunner/global_settings.py", line 42, in def findInPath(fileName, path=os.environ['PATH']): File "/usr/lib/python2.5/UserDict.py", line 22, in __getitem__ raise KeyError(key) KeyError: 'PATH' }}} Near the top of the traceback you'll find mention of a Launchpad branch, probably {{{canonical/lp-branches/devel}}} or {{{canonical/lp-branches/trunk}}}. From that branch, remove two imports: * From {{{lib/lp/testing/__init__.py}}} remove this import: {{{ from windmill.authoring import WindmillTestClient }}} * From {{{lib/canonical/testing/layers.py}}} remove this: {{{ from windmill.bin.admin_lib import ( start_windmill, teardown as windmill_teardown) }}} Now restart Apache. == Setting up the testing environment in a branch == * Create a Launchpad source tree, and cd into it. * Substituting your email address, but ''not'' one that is also in the sample data, run (parts may fail, but it's probably okay): {{{ make schema make run_codehosting >/dev/null 2>&1 & # Wait until that's all up and running... utilities/start-dev-soyuz.sh utilities/soyuz-sampledata-setup.py -e }}} == Preparing the slave == Follow the instructions for setting up a local buildd slave at [[BuildFarm/TryOutBuildSlave]]. Skip the part where it tells you to run Launchpad, since you're already running it. You should end up with a shell open in a chroot for your simulated build slave. Keep it running; we're going to use that slave! Did you obtain the chroot tarball as described on that page? Good. Give it to your running Launchpad instance and tell it to use this for its chroot (in this example, lucid): {{{ scripts/ftpmaster-tools/manage-chroot.py -s lucid -a i386 add -f chroot-ubuntu-lucid-i386.tar.bz2 }}} == Making some branch updates to generate templates from == * Open https://launchpad.test/ in browser, log in as , with password "test" * Create project "bf-test" for ppa-user at https://launchpad.test/projects/+new * Register hosted branch "bf-test" for the project at https://code.launchpad.test/bf-test/+addbranch * Link branch to trunk at https://launchpad.test/bf-test/trunk/+linkbranch * Enable translations for project at https://launchpad.test/bf-test/+configure-translations * Enable template imports for trunk at https://translations.launchpad.test/bf-test/trunk/+translations-settings * Create a branch, or steal one. Just paste into a terminal (you may be prompted for your GPG passphrase): {{{ bzr push -d lp:gedit lp://dev/bf-test --remember --use-existing-dir }}} '''Or hack it up locally, even though template generation probably won't quite work:''' {{{ pushd /tmp bzr init bf-test cd bf-test cat <test.c #include #include main(){puts(_("Hi"));} EOF mkdir po echo test.c >po/POTFILES.in bzr add test.c bzr add po bzr add po/POTFILES.in bzr commit -m "Setting up fake intltool branch." bzr push lp://dev/bf-test --remember --use-existing-dir popd }}} * Back in your branch: {{{make sync_branches}}} Now you should have a {{{TranslationTemplatesBuildJob}}} sitting in the {{{BranchJob}}} table. You should see a very wide line of data coming out of: {{{ psql launchpad_dev -c ' select * from branchjob join job on job.id=branchjob.job join buildqueue on buildqueue.job=job.id where branchjob.job_type=6 order by job.id' }}} It will show a {{{branch_url}}} parameter to be passed to the slave, pointing to your branch: http://bazaar.launchpad.test/~ppa-user/bf-test/bf-test /!\ Some system setups apparently can't access this branch. Try this: {{{ pushd /tmp bzr export export-experiment http://bazaar.launchpad.test/~ppa-user/bf-test/bf-test }}} If that succeeds and creates a copy of bf-test in a directory called export-experiment, then it's fine; otherwise, re-do your rocketfuel setup by running {{{rocketfuel-setup}}}. And remove your branch. And start over. Sorry! == Simulating a builder == Now we tell Soyuz that your local buildd slave is in fact Bob the Builder. Logged in as an admin (I suggest using a different browser so as not to break your ongoing session), check the Virtualized checkbox at https://launchpad.test/builders/bob/+edit and enter an arbitrary hostname under Virtual Machine Host. Clear the "Builder State OK" checkbox to convince it not to continue building firefox for hoary, as it's been trying to do for the past few years. Submit. Wait for a few seconds. Go back to the form and re-check "Builder State OK." Submit. == Running the job on the slave == After a while, the buildd master should dispatch your job to Bob the Builder, running in your slave. Keep an eye on these pages: * https://launchpad.test/builders (builders overview) * https://launchpad.test/builders/bob (Bob the Builder) * https://launchpad.test/builders/bob/+history (build history for Bob the Builder) '''This should kick off the job and produce a template on the import queue for {{{bf-test}}}.''' = Cleanup = To undo the changes made by {{{utilities/soyuz-sampledata-setup.py}}}: * {{{rm -f /var/tmp/zeca/*}}} * {{{make schema}}}