DXR deployment: Difference between revisions
No edit summary |
|||
| Line 2: | Line 2: | ||
== dxr.mozilla.org == | == dxr.mozilla.org == | ||
Builds are done via special tinderbox runs that happen hourly. They show up on tbpl under Linux64 opt | Builds are done via special tinderbox runs that happen hourly. They show up as [https://tbpl.mozilla.org/?noignore=1&jobname=dxr-mozilla-central hidden builds on tbpl] under Linux64 opt. The buildbot script that is run can be found [http://hg.mozilla.org/build/tools/file/tip/scripts/dxr/ 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 [http://ftp.mozilla.org/pub/mozilla.org/dxr/ 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 that is currently at [http://hg.mozilla.org/projects/dxr]. This is a mirror of the github repository. This is automatically updated at 0:00 Pacific from the master 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. | Builds run using code that is currently at [http://hg.mozilla.org/projects/dxr]. This is a mirror of the github repository which only pushes changes from the prod branch of github. This is automatically updated at 0:00 Pacific from the master 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 == | == dxr.allizom.org == | ||
Revision as of 21:54, 30 January 2013
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 that is currently at [1]. This is a mirror of the github repository which only pushes changes from the prod branch of github. This is automatically updated at 0:00 Pacific from the master 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.