Ticket #2310 (closed enhancement: fixed)
upgrade-master doesn't support master.cfg located outside of basedir
| Reported by: | KeiKun | Owned by: | |
|---|---|---|---|
| Priority: | patches-accepted | Milestone: | 0.8.8 |
| Version: | 0.8.6p1 | Keywords: | simple |
| Cc: |
Description (last modified by dustin) (diff)
Some buildbot subcommands (e.g., buildbot checkconfig) currently assume that Buildbot's configuration file is named master.cfg, and is located in the master's basedir. This is not always the case. The name amd location of the config file are specified in the master's buildbot.tac, which is always in the basedir.
All of the buildbot subcommands should support a master.cfg that is not in the default location. Tests should verify that this is the case.
At least 'buildbot checkconfig' and 'buildbot upgrade-master' do not work correctly.
Change History
comment:2 Changed 12 months ago by tom.prince
- Keywords simple added; master,svn removed
- Priority changed from minor to trivial
- Summary changed from Change master.cfg path to upgrade-master doesn't support master.cfg located outside of basedir
- Milestone changed from undecided to 0.8.+
comment:3 Changed 6 months ago by tom.prince
- Owner set to tom.prince
- Status changed from new to assigned
comment:5 Changed 3 months ago by dustin
- Owner tom.prince deleted
- Description modified (diff)
I'm rewriting this description for contributors. Previous description:
Hi!
i was trying to change my master.cfg location like for example its my buildmaster is located at /home/user/master/ (and so as my master.cfg is found) i wanna change my master.cfg location to /home/user/buildbot/
i tried editing
configfile = r'master.cfg' to configfile = r'/home/user/buildbot/master.cfg'
but still buildbot is finding the master.cfg in /home/user/master/ why is this happening
comment:7 Changed 2 months ago by dustin
- Status changed from assigned to closed
- Resolution set to fixed
- Description modified (diff)
commit 69fc8c7a0ca7084b3b2e5ea93c613cdec3ffc2d6
Merge: 16e9ede 7f02964
Author: Dustin J. Mitchell <dustin@mozilla.com>
Date: Tue Mar 19 16:26:44 2013 -0400
Merge branch 'ticket2310' of git://github.com/imccowan/buildbot
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)
okay i guess the problem about my report is i didn't specified it but anyways i guess its my fault either i didn't tell that i was using 2 commands since before you run you do a test. now since the command "buildbot start" works fine now. after changing the new path of the master.cfg. i was wondering now why the other commands still uses old path of master.cfg. for example since "buildbot start" works without other things not like the other 2 commands("buildbot checkconfig" and "buildbot reconfig") requires path of new master.cfg like as my issue was /home/user/buildbot ("buildbot checkconfig /home/user/buildbot/master.cfg") for the command to work.
Im saying.. Why those 2 commands requires the New path of master.cfg for it to work. isn't it when you run those commands it will automatically use the new path of master.cfg instead of the old one?