DXR deployment

This page consists of notes about how DXR is deployed at Mozilla, to save you from having to read through several bug information.

dxr.mozilla.org

Builds are done via special tinderbox runs that happen hourly. They show up as hidden builds on tbpl under Linux64 opt. The buildbot script that is run can be found here. This uses some more scripts to actually do the DXR indexing located ??? I don't know where, jonasfj might know? The completed tarballs are uploaded to the ftp server, which are polled by the server and downloaded every hour; the server-update script is designed to make the web-public switch atomic.

Builds run using code from an hg mirror of the github repository which automatically updated every hour from the prod branch at github, via a cronjob (on repomgr.ateam.phx1.mozilla.com which lives in MPT). Talk to mdas if you have any problems with the git->hg mirror. If you have sudoer access to this machine, the jobs are run under the 'ateamauto' user.

dxr.allizom.org

This is uploaded manually by jonasfj every now and then. I know nothing else.

dxr development

DXR is integrated with Jenkins so that tests are run after a pull request is merged. A separate Jenkins job run by LeeroyBot will test PR's as they are opened and updated, and report the results on the Pull Request itself.