Closed Bug 245574 Opened 21 years ago Closed 19 years ago

tinderbox should re-read configuration in each cycle

Categories

(Webtools Graveyard :: Tinderbox, enhancement)

Product:
Webtools Graveyard
Component:
Tinderbox
Platform:
x86
Linux
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: Biesinger, Assigned: mcafee)

Details

it would be nice if tinderbox would read tinder-config.pl at the start of each cycle, so that restarting it explicitly is not necessary.
yes, we could probably do this. It probably never got to this point because I/we/whomever would want the change to start as soon as the file was edited, this required interrupting the current cycle.
mozbot has code to do this. i've been lazy and just go to the screen and kill and restart it. (i've sort of wanted this for years)
(In reply to comment #2) > mozbot has code to do this. i've been lazy and just go to the screen and kill > and restart it. (i've sort of wanted this for years) I dislike the yellow stripe this causes on tbox though :)
The latest version of tinderbox does this (it's why the autoupdate config feature works).
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Is this a local change, or am I just unable to find the right place in the code frm CVS?
Adding rhelmer, who marked this bug fixed. Robert, a question for you in comment #5.
Yes I should really clarify.. when using multi-tinderbox (e.g. "./tinderbox multi start" and an appropriate multi-config.pl), the config will be re-read each time, since build-seamonkey.pl is being invoked with "--once". If you are running e.g. build-seamonkey.pl without "--once", the config will not be re-read on each run. Maybe --once should be the default for build-seamonkey.pl, and it should be assumed that it's started from multi-tinderbox (or e.g. cron)? Is there any advantage to adding code for build-seamonkey.pl to be able to manage itself? Other tools can do that task better.
>Maybe --once should be the default for build-seamonkey.pl, and it should be >assumed that it's started from multi-tinderbox (or e.g. cron)? Is there any >advantage to adding code for build-seamonkey.pl to be able to manage itself? If that's the recommended configuration then README/INSTALL should probably describe that.
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.