Difference between revisions of "Talk:Tinderbox Setup"
| Line 6: | Line 6: | ||
And a (prominent) link to the actual tinerbox would be nice too :-) [[User:Cloph|Cloph]] | And a (prominent) link to the actual tinerbox would be nice too :-) [[User:Cloph|Cloph]] | ||
| − | Indeed, any ideas where? tools.openoffice.org? | + | Indeed, any ideas where? tools.openoffice.org? [[User:vq|vq]] |
== What about support for shadow-trees? == | == What about support for shadow-trees? == | ||
| Line 23: | Line 23: | ||
On *NIX use lndir to link the master directories | On *NIX use lndir to link the master directories | ||
into the src_path, on Windows use cp instead. | into the src_path, on Windows use cp instead. | ||
| + | |||
| + | [[User:vq|vq]] | ||
Revision as of 18:46, 16 January 2006
Would it be possible to modify the tinderbox to just accept the build-status & logs that are generated by "build --all --html" (has per-module logs, etc. the script would only have to zip all the logs from the output-dirs)
Yes, sure, but you can also provide a short script that collects the build scripts and cats them together.
And a (prominent) link to the actual tinerbox would be nice too :-) Cloph
Indeed, any ideas where? tools.openoffice.org? vq
What about support for shadow-trees?
Would it be possible to enhance the scripts so they work with a shadow-tree of an already present checkout?
Have the master (e.g. SRC680_m148) as normal checkout, then make shadowtree, build the master. After that, clean-up, make another shadowtree, update that tree to a given cws, build the cws, after that clean up... Cloph
How about an extra--shadowswitch for tinget.pl? Like this:
tinget cl27 my_cl27.log /my/current/ws up --shadow /my/SRC680_m150/checkout
Description for this switch:
--shadow shadowpath - Use the shadowpath directory as a source for the
MWS instead if using cvs operations.
On *NIX use lndir to link the master directories
into the src_path, on Windows use cp instead.
