ReleaseEngineering/Applications/Mapper: Difference between revisions

ReleaseEngineering/Applications/Mapper (view source)

20 bytes added , 4 November 2014

m

markup fix

Confirmed users

1,351

edits

@@ Line 49: / Line 49: @@
 mapper expects hggit map files to be available under the 'mapfiles' directory of the application. On cruncher, these are in /home/buildduty/mapper/mapfiles. Each subdirectory of mapfiles corresponds loosely to a different repository being tracked. On cruncher, the mapfiles for each of these projects are symlinked to the mapfiles being published to cruncher via the process outlined above.
-Legacy vcs-sync provides mapfile information for the following repository groupings. ''(These can be seen via "``ls */mapfile-needed``" in the legacy configs directory.)''
+Legacy vcs-sync provides mapfile information for the following repository groupings. ''(These can be seen via "<tt>ls */mapfile-needed</tt>" in the legacy configs directory.)''
-* git -> hg from ``gaia.git`` code to ``integration/*`` (11 repositories configured)
+* git -> hg from <tt>gaia.git</tt> code to <tt>integration/*</tt> (11 repositories configured)
 * hg -> git for gaia L10N (75 repositories configured)
 * hg -> git for gecko L10N (50 repositories configured)
-* hg -> git for gecko.git (15 repositories configured - from ``releases-gecko/hgrc``)
+* hg -> git for gecko.git (15 repositories configured - from <tt>releases-gecko/hgrc</tt>)
 ''Note that the above docs will be integrated into the wiki after vcs-sync development stabilizes.''