Hi all, does anyone use/try this feature? I would like to develop it further, but first I need feedback. Best regards,
Vladimir Vladimir Glazounov wrote: > Hi all, > > RE presents with SRC680 m212 the build tool's new feature. Now it is > possible to make distributed builds, ie - build one CWS/workspace using > multiple machines. > The usage is simple: you start client(s) on machines, that should be > used for builds, and "build --server" on the "master" machine. Client > machines should be usable as build machines, and they should have the > same paths to the sources as the master has. > > ======================================================================= > Usage: > master: > build --master --setenvstring "setenv_string" [--port PORT] > > setenv_string - the command for setting the build environment > (imho > should be the same as used for master environment). > Does not need to be specified in SO(setsolar) environment > > PORT - port number for server (default is one of range > > 7890-7894, assigned automatically) > > client: > build_client [-PN] host[:port1:...:portN]|@server_list_file > > -PN - number of client process to start. Each client process > operates as a independent client. > > host[:port1:...:portN] - host/ports from which the jobs can > be accepted. There can be multiple hosts/ports at the same time. > Default - the client tries to connect the ports 7890-7894 of > each master > > @server_list_file - path to the text file with server list, > specified as host1[:port1:...:portN] [host2[:port1:...:portN] > the file can be changed in the runtime - the changes will be > noticed > by the client > ======================================================================= > > This description is not complete, it covers basic usage. More detailed > description deliver the tools themselves... > > The build tool in the master mode writes a html page, where one can see > the progress of the build process. The page is here(per default): > $SOLARSRC/$INPATH.build.html > All other features of the build tool are not changed. > > I made a test on linux, and here are the results: > complete OOo local build on one machine: 4h 59m > complete OOo build on two machines, one machine - locally, another - > over nfs: 3h 07m > These results can be different on different OS, CPU, infrastructure. > > I hope this feature will be useful. > Have fun, > > Vladimir > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
