24
edits
Tinderbox/Tbox3 tests: Difference between revisions
m
Changed format a little.
(Added details for how Mozilla builds using tinderclient) |
m (Changed format a little.) |
||
| Line 16: | Line 16: | ||
=== History, or How does Mozilla do it? === | === History, or How does Mozilla do it? === | ||
The original Mozilla specific tbox3 tinderclient has 4 modules that get run, one after the other: | The original Mozilla specific tbox3 tinderclient has 4 modules that get run, one after the other: | ||
; init_tree:Pulls the code from CVS and prepares to build. If there are new changes that require a build, then <code>SHOULD_BUILD</code> is set; otherwise, it's left 0, so only the tests run continuoulsy if no one checks in code (this may be an oversight). | |||
; build : If <code>SHOULD_BUILD</code> is set, it will call "make" to make the build. | |||
; distribute:The distribute module looks at the argument (or Var) distribute, which defaults to "build_zip". Then for each module, if <code>SHOULD_BUILD</code>, it calls the module (which does a "make packager", or creates some other zip file), and then scps the build to the server. | |||
;tests:The tests module looked at the argument (or Var) "tests" (which defaults to "Tp,Ts,Txul") Then tests calls each of the arguments as a module (so TinderClient::Modules::Tp gets called, TinderClient::Modules::Ts, etc) | |||
=== Details, Details, Details === | === Details, Details, Details === | ||