Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update information

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@146099 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
kestes%walrus.com 2003-08-17 00:36:57 +00:00
parent b3c377316b
commit 62b721eb14
3 changed files with 42 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
mozilla/webtools/tinderbox2/ChangeLog
View File

@ -1,3 +1,9 @@
New Time columns for use in environments with multiple time zones.
Spelling fixes
Add support for popup windows which work "on click"
Add support for users who want to see tinderbox's notion of what was

18
mozilla/webtools/tinderbox2/Install
View File

@ -219,7 +219,9 @@ hostname/modules exactly as you wrote it in VCData. Then copy your
must be the REAL home of the Tinderbox daemon, as listed in
/etc/passwd/ and set in the $HOME environmental variable for
tinder.cgi. The file must not be world readable or writable or
executable.
executable. It is recommended that VC_CVS.pm is only used as an
interim step in setting up VC_Bonsai. VC_Bonsai is not hard to setup
and provided many useful features which are absent in VC_CVS.pm.
*) Setup the build machines to mail their build logs (with tinderbox
@ -234,6 +236,16 @@ look like. There is an example mail in the test directory called
samplelog. The clientbin directory contains code which can be used on
the buildmachine. See the README to help setup your buildmachine.
http://www.ntsendmail.com/ has a perl program which can be used to
send mail on systems where there is no sendmail installed.
There is nothing special about sending mail. Any data transport layer
would work including HTTP Post and SSH the only requirement is that
the data is sent to the STDIN of the mail processing programs upon
delivery and that the process which runs this is the same uid as the
tinderbox server. I have not thought too much about how to set up
these alternate delivery mechanisms so I have no practical advice but
It should not be too hard to setup.
*) Set up the bug tracking system to send mail to 'tinderbox_bugs' on
the webserver machine whenever a Bug ticket changes state. It is not
@ -248,7 +260,7 @@ machines that it will be received by someone who can act on it.
I keep my email up to date in the source code. If you have trouble
with these instructions please drop me a line.
I keep my email up to date in the Contact file. If you have trouble
with these instructions please drop me a line.
Ken Estes.

21
mozilla/webtools/tinderbox2/Todo
View File

@ -25,3 +25,24 @@ It would be really nice if CVS could mail tinderbox the updates which
apply to the branches of interest, then tinderbox would not have to
poll and it would get the branch information which it needs.
I would be interested in a module VCDisplay module to work with this
bonsai work alike tool http://viewcvs.sourceforge.net/ but I do not
have time not to investigate it. This should be simple to code once
viewcvs is setup, it may even be exactly the same as
VCDisplay::Bonsai.
I had one user who used the new Perforce modules but they reported
problems with the data gathering capability. They did not give me
enough info to fix the problem. Any help here would be apreciated.
VCDisplay::Perforce_P4DB appears to work.
I would like to have a compression library which can be used to
compress and uncompress logs so that the transit of those logs is
compressed. The difficulty here is that the library should be
flexible. Perhaps the build machines do not have the perl compression
libraries but do have the compression binaries it may be the reverse
situatuation on the server. Also We should support many kinds of
compression/encryption (uuencode, ascii armor) and other data
transforms so that users can configure the mail to use compression
followed by pgp followed by ascii armor or something like that.