Revision: 7765
Author: [email protected]
Date: Tue Mar 23 08:23:58 2010
Log: Fixed unintended WikiWords, added comment about shared filesystem.
http://code.google.com/p/google-web-toolkit/source/detail?r=7765
Modified:
/wiki/DistributedBuilds.wiki
=======================================
--- /wiki/DistributedBuilds.wiki Tue Mar 23 07:38:01 2010
+++ /wiki/DistributedBuilds.wiki Tue Mar 23 08:23:58 2010
@@ -7,16 +7,16 @@
= Details =
-A distributed GWT build has three stages: Precompile, CompilePerms, and
Link. Precompile and Link normally run on the main build node. One
instance of CompilePerms runs per permutation, and those instances run in
parallel, on multiple nodes.
-
-All three commands take a -workDir argument. Specify a directory where
they can place their outputs and read their inputs. The items placed there
by Precompile need to be copied to the machines that run CompilePerms, and
the files that result from all the CompilePerms runs need to be copied back
to the directory on the start node before running Link.
+A distributed GWT build has three stages: Precompile, !CompilePerms, and
Link. Precompile and Link normally run on the main build node. One
instance of !CompilePerms runs per permutation, and those instances can run
in parallel, on multiple nodes.
+
+All three commands take a -workDir argument. Specify a directory where
they can place their outputs and read their inputs. The items placed there
by Precompile need to be shared between the three stages -- either via a
shared filesystem or by copying the contents after Precompile to the
machines that run !CompilePerms, then copying back all the files that
result from all the !CompilePerms runs before running Link.
The Precompile command takes a module name as input and emits a file
precompilation.ser into the work directory. Here's a typical command line:
{{{
java -cp ... com.google.gwt.dev.Precompile
com.google.gwt.sample.hello.Hello \
-workDir work
}}}
-The CompilePerms command takes a module name and a list of permutations
that it should compile. The permutations are numbered sequentially
starting from 0. It is up to the embedding build system to know the number
of permutations and run the right number of instances of CompilePerms.
Here is a typical set of commands to run:
+The !CompilePerms command takes a module name and a list of permutations
that it should compile. The permutations are numbered sequentially
starting from 0. It is up to the embedding build system to know the number
of permutations and run the right number of instances of !CompilePerms.
Here is a typical set of commands to run:
{{{
java -cp ... com.google.gwt.dev.CompilePerms
com.google.gwt.sample.hello.Hello \
-workDir work
@@ -51,4 +51,4 @@
= Parallel build systems =
-The three-stage entry points described above allow GWT to be used in
distributed builds, but GWT does not include a distributed builder. Any
project wanting a distributed build needs to work out a distributed build
system. It's possible to get by using ssh and scp, but it's probably
easier to use a dedicated tool like Hudson, CruiseControl, or Pulse.
+The three-stage entry points described above allow GWT to be used in
distributed builds, but GWT does not include a distributed builder. Any
project wanting a distributed build needs to work out a distributed build
system. It's possible to get by using ssh and scp, but it's probably
easier to use a dedicated tool like Hudson, !CruiseControl, or Pulse.
--
http://groups.google.com/group/Google-Web-Toolkit-Contributors
To unsubscribe from this group, send email to
google-web-toolkit-contributors+unsubscribegooglegroups.com or reply to this email with
the words "REMOVE ME" as the subject.
