buildsys October 2005

buildsys@lists.fedoraproject.org

10 participants
18 discussions

Start a nNew thread

Extras build system back up
by Dan Williams 26 Oct '06

26 Oct '06

Hi, We're back up and using the latest plague code. yum update your plague-client and you should be good to go. Dan

3 7

Patch to store user info in different DB engines
by Jeff Sheltren 29 Nov '05

29 Nov '05

I'm attaching a patch which uses DBManager for interacting with the user database rather than always relying upon sqlite. This way, if you use pgsql or mysql for your database back-end, user information will be stored there as well. The problem is, this will screw up current installations which are using pgsql/mysql because the old code assumes sqlite is used for user info, so suddenly your user database will be empty... I guess the easiest way around this is to write a quick script to pull everything out of the sqlite database and put it into mysql/pgsql. Also, I'll look at updating the user-manager.py script. In fact, I guess it may be easiest to add export/import functions to that for migrating the user info. Let me know what you think. -Jeff

3 16

[patch] Patch to fix double call to "mock clean" in case, if mock will failed on "prep" stage.
by Alexandr Kanevskiy 31 Oct '05

31 Oct '05

Hi all. I found one small issue, that in case of mock will fail on prep stage (no space on device, or repository access failed) mock will return earlier, and in _status_prepping(), _watch_mock function will call _start_cleanup(). After that _start_cleanup will change next state to be "cleanup". But, this "if" below, will change next status to "building" regardless of previous error: if not self._mock_using_repo(): self._status = 'building' that meas scenario: _status_prepping _watch_mock mock clean _status_building _watch_mock mock clean Attached patch solves that. -- Alexandr Kanevskiy.

2 2

RFE: mock kill
by Oliver Falk 31 Oct '05

31 Oct '05

Hi! I allready wrote Seth and he asked me to write it to the list - so here we go. I'd like to have a mock command 'kill'. If I run a mock-build process it runs all chroot command as root and if I want to stop mock from running as a normal user I can't.... So a 'mock kill -r <target> --uniqueext <randomstring_or_whatever> kill' would be a great thing. :-) Best, Oliver

1 0

Patch to honor configfile flag
by Jeff Sheltren 27 Oct '05

27 Oct '05

Currently the configfile /etc/plague/server/plague-server.cfg is hard coded in plague-server, and it will not use a different file even if specified with the -c option. This patch changes plague-server to use the config file specified with -c, and also sets a default of / etc/plague/server/plague-server.cfg so that you do not have to use the -c option if you want to use the default config location. -Jeff

2 2

plague-server dying
by Jeff Sheltren 26 Oct '05

26 Oct '05

I am having problems with plague-server dying on me. I am starting plague-server like: plague-server -c /etc/plague/server/plague-server.cfg -d -l /var/log/ plague/plague.log my.ip.address.here After some amount of time (hours? I'm not sure exactly, but I know it was up all most of the day yesterday and then died sometime in the night) the process disappears, and nothing is left in the log file except for the startup and build messages. Is there anything I can do to have it print out more information? I am running the server on an EL4 box, might that have something to do with it? plague-server is CVS from a few days ago (using mysql back-end patch). python version is python-2.3.4-14.1 I also have plague-builder running on the same box, and it has been running with no problem. Thanks, Jeff

2 4

Mock Patch to Enable Realtime Output of logs
by Jeff Pitman 25 Oct '05

25 Oct '05

Hi: This patch allows one to run "tail -f" on the build.log. It mostly re-uses existing variables and things like resultdir, etc. work properly. Anyway, I hope to get this committed as this is a massive improvement from what mock had inherited. (Multiple mount/umount in root.log, but I don't think that many people care. It's the simplest patch without taking in account of corner cases, etc.) -- -jeff

3 6

Docs & Examples
by Jeff Sheltren 24 Oct '05

24 Oct '05

OK, I got plague-(server/builder) working - yay! The README in CVS is pretty helpful, but I still had to do a lot of guesswork and reading through the code in order to figure out how to set it up. I think it would be very helpful to provide example config files (with comments explaining what each setting does, and a list of valid settings if applicable), and some more documentation. I'd be happy to help with this - anyone mind if I create some docs/examples subpages from the Plague wiki page? At least I can put up my config files (and try to comment in them a bit), show some example targets, document how I got the www scripts working with apache, etc. -Jeff

4 7

plague-server && mysql
by Chris Weyl 24 Oct '05

24 Oct '05

Hey all-- I can't post a patch for various reasons beyond my control (sigh...), but updating plague to use a mysql backend was trivial. (Not that I don't like postgresql -- mysql is just easier for me in this environment.) 1) yum install MySQL-python 2) edit /usr/share/plague/server/DBManager.py: * copy the pgdbEngineClass definition verbatim, renaming it to 'mysqlEngineClass' * the correct type for mysql in get_uid_field_type is - "int(11) NOT NULL auto_increment PRIMARY KEY" * connect parameters are slightly different in _connect(): - host=host, db=database, user=user, passwd=password * add the new class to the db_engines array * add a try statement to importing the MySQLdb class 3) update your plague-server.cfg with a "[mysql Engine]" section And, of course, create your mysql db somewhere, etc, etc. Hope that helps someone! :) -Chris

3 6

builds seeming to hang in "add_to_repo/in-progress"
by Chris Weyl 21 Oct '05

21 Oct '05

Hey Dan (et al) -- So now I can build from CVS, everything appears OK... Except packages (that don't fail) seem to hang in the "add_to_repo/in-progress" state. The log files from the build appear in the expected place. However, build.log is 0 bytes. The SRPM does not show up here. In plague-server.cfg, [General] repo_script = testing = False Trying to do a "plague-client finish #" on the jobids fails with the expected "Error: Job 9 must be either 'needsign' or 'failed' to finish it." Am I missing something? Or is something darker and more sinister at work here. -Chris

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys October 2005