== Building Sync ==
The party line to rebuild the tree after making changes Sync code is to runalmost exclusively JavaScript, and so you probably should build using an artifact build, as described [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Artifact_builds here].
$ make After setting this up, you'll do `mach build` to perform a build, `mach run` to run Firefox, and `mach xpcshell-f clienttest /services/sync/tests/unit` to run the sync unit test suite.mk or from the object directoryThere's also a separate end-to-end test suite, TPS, which is documented [https: $ make //developer.mozilla.org/en-sj8US/docs/Mozilla/Projects/TPS_Tests here]. (For most changes its sufficient you run the unit tests)
However, this is slow. If you have simply changed a JS file in ''services/sync/'', it is sufficient to run the following from Depending on your object directory: $ make -sj8 -C services/sync The xpcshell tests will pick up changes immediately. HoweverOS, if you launch Firefox, your most changes '''won't''' be reflected. For that, you'll also need to will not require a rebuild the browser component: $ make -sj8 -C services/sync && make -sj8 -C browser A handy alias to have around is: $ alias sync-launch make -sj8 -C services/sync && make -sj8 -C browser && dist/bin/firefox -no-remote -ProfileManager Ortake effect, on OS X: $ alias sync-launch make -sj8 -C services/sync && make -sj8 -C browser && dist/NightlyDebugonly restarting and rerunning via `mach run`.app/Contents/MacOS/ -no-remote -ProfileManager
= Using Bugzilla =
