Ticket #527 (closed enhancement: fixed)
make "buildbot start" directory optional
| Reported by: | ipv6guru | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.7.12 |
| Version: | 0.7.10 | Keywords: | sourceforge 1517959 |
| Cc: |
Description (last modified by dustin) (diff)
How about making the directory be an optional parameter when doing "buildbot start"?
As an example, it would be great if each of these did the same identical thing:
% buildbot start % buildbot start . % buildbot start /home/foo/buildbotconfig (when run from the /home/foo/buildbotconfig directory)
Submitted: John O'Duinn ( joduinn ) - 2006-07-06 15:22
Extra Comments :-
ate: 2007-01-31 09:50 Sender: warner
yeah, that sounds reasonable to me. 'stop' and 'restart' should do the same thing, of course.
Change History
comment:2 Changed 4 years ago by dustin
- Status changed from new to closed
- Resolution set to wontfix
- Description modified (diff)
The buildmaster needs a directory to store stuff in, and I don't want to just strip the filename from the config file and use that -- doing so violates the principle of least surprise..
comment:3 Changed 4 years ago by marcusl
But if there's a master.cfg or rathrt buildbot.tac in the current dir, isn't it obvious it's a buildmaster directory?
comment:4 Changed 4 years ago by dustin
Oh, I misread the OP as saying that 'buildbot start' woud accept a path to a config file.
So yeah, this sounds fine.
comment:6 Changed 4 years ago by dustin
- Status changed from closed to reopened
- Resolution wontfix deleted
comment:7 Changed 3 years ago by dustin
- Status changed from reopened to closed
- Resolution set to fixed
- Milestone changed from 0.8.+ to 0.7.12
commit af5c745b6a8a8332a4d73caaef5ba9c43491d60a
Author: Daniel Dunbar <daniel@zuster.org>
Date: Sun Dec 27 14:04:05 2009 -0800
Trac #527: make "buildbot start" directory optional.
Thanks Daniel!
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
Moved from sourceforge