buildsys August 2005

buildsys@lists.fedoraproject.org

11 participants
13 discussions

Some mock ideas
by Ignacio Vazquez-Abrams 31 Aug '05

31 Aug '05

I've been running through some ideas in my head over the past couple of days, and here's what I've come up with. 1) Instead of including config files in the base mock package, put them in mock-config-<distro>-<distro version> packages so that mock configs are easy to add via packages. (Corollary: use alternatives for default.cfg) 2) Include the buildgroups data in the config packages. There could also be a /etc/httpd/conf.d/buildgroups.conf file in the base package that would point to the buildgroup data in /usr/share/mock. 3) Make mock use yum as a module. That way you wouldn't need to invoke yum as an external program and you could have more-fine-grained control over it. 4) Have mock be a module that plague-builder could import. See the rationale for the previous point, but replace mock for yum. Any comments? -- Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net> http://fedora.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

4 6

Patch to put mockbuild results in $WORKDIR
by Ignacio Vazquez-Abrams 29 Aug '05

29 Aug '05

The attached patch makes the results of mockbuild end up under $WORKDIR. -- Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net> http://fedora.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

3 3

Sign & Push removal from needsign
by Warren Togami 26 Aug '05

26 Aug '05

http://buildsys.fedoraproject.org/build-status/success.psp What event happens and how often does sign & push cause packages from needsign to disappear? About 4 hours after the last sign & push and nothing has disappeared. Warren Togami wtogami(a)redhat.com

2 1

Traceback after package build
by Warren Togami 24 Aug '05

24 Aug '05

http://buildsys.fedoraproject.org/logs//development/329-monotone-0.22-4.fc5… http://buildsys.fedoraproject.org/logs//development/329-monotone-0.22-4.fc5… setup build ending Traceback (most recent call last): File "/usr/bin/mock", line 786, in ? main() File "/usr/bin/mock", line 781, in main my.close() File "/usr/bin/mock", line 343, in close self._umount_by_file() File "/usr/bin/mock", line 429, in _umount_by_file self._umount(item) File "/usr/bin/mock", line 406, in _umount (retval, output) = self.do(command) File "/usr/bin/mock", line 445, in do return (retval, output) UnboundLocalError: local variable 'retval' referenced before assignment Cleaning up the buildroot... /usr/bin/setarch ppc32 /usr/bin/mock clean --uniqueext=b3cd6c7b101ba3bd91f6b7550f776c7d486e316a -r fedora-development-ppc-core

3 2

Stuff to look for in plague 0.4
by Dan Williams 23 Aug '05

23 Aug '05

Quite a few things will change for plague 0.4: o Single builder, multiple jobs: you'll only have to run one builder instance on a machine to run multiple build jobs; each builder will be able to build a set number of jobs at a time (usually equal to # of processors). - Architectures are autodetected o New config file format: it's now using ConfigParser, which means more straightforward and text-friendly config files, for both the server and the builder. o Targets get their own config files: each target, on the server and on the builder, gets its own config file. This means a few things: - each target can have its own CVS settings - each target can be a different distribution o Scratch/Testing targets: targets that don't contribute packages tothe repository, so you can test out your packages before you actually push them through. Scratch targets also don't kill a job when one architecture fails. If anyone has more thoughts, file some RFEs in bugzilla for Fedora Extras Infrastructure. Dan

5 7

Extras build system upgrade notice
by Dan Williams 15 Aug '05

15 Aug '05

Hi, Seth, Jeremy, and I are upgrading the Extras build system today. We'll send out the announcement when the upgrade is complete, which is likely to take until late Monday afternoon, US EST, to get all the pieces together. Here are some things to expect: o You immediately see the Job ID that you just enqueued o The Web interface is easier to follow, the most relevant jobs are at the top of the page o We'll be running 2 PPC builders (hopefully), so PPC should keep up more easily o Users and their permissions can be changed on the fly, no more waiting to get added to the database What you need to do: o 'yum update plague' so that you have the latest plague-0.3 RPMs. Once the system is up, we'll push through FC-3 and FC-4 plague RPMs for those who aren't running Rawhide. Dan

1 1

Setting up plague server - Difficulty w/ SSL setup
by Jesse Keating 09 Aug '05

09 Aug '05

I'm following the README in the plague package, and I'm having trouble w/ step 6 of Configuring SSL for your Build System. <quote> 6. Sign the build server certificate request with the BSCA certificate openssl ca -out server_cert.pem -infiles server_req.pem <endquote> If I run this, I get: [root@plague server]# openssl ca -out server_cert.pem -infiles server_req.pem Using configuration from /usr/share/ssl/openssl.cnf Error opening CA private key ./demoCA/private/cakey.pem 18008:error:02001002:system library:fopen:No such file or directory:bss_file.c:259:fopen('./demoCA/private/cakey.pem','r') 18008:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:261: unable to load CA private key So it would seem I need to specify the CA private key so I try: [root@plague server]# openssl ca -keyfile /root/CERTS/CA/private/ca_key.pem -out server_cert.pem -infiles server_req.pem Using configuration from /usr/share/ssl/openssl.cnf Error opening CA certificate ./demoCA/cacert.pem 18085:error:02001002:system library:fopen:No such file or directory:bss_file.c:259:fopen('./demoCA/cacert.pem','r') 18085:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:261: unable to load certificate Now I'm missing the cert... one more step: [root@plague server]# openssl ca -keyfile /root/CERTS/CA/private/ca_key.pem -cert /root/CERTS/CA/ca_cert.pem -out server_cert.pem -infiles server_req.pem Using configuration from /usr/share/ssl/openssl.cnf I am unable to access the ./demoCA/newcerts directory ./demoCA/newcerts: No such file or directory Still no juice. Not sure why it is trying to access the newcerts file. Can anybody help me with what I'm doing wrong here, or help me generate a patch to the documentation that will lead people in the right direction? -- Jesse Keating RHCE (http://geek.j2solutions.net) Fedora Legacy Team (http://www.fedoralegacy.org) GPG Public Key (http://geek.j2solutions.net/jkeating.j2solutions.pub) Was I helpful? Let others know: http://svcs.affero.net/rm.php?r=jkeating

4 4

patch to add SuSE 9.3 support to mock
by Bryan Stillwell 09 Aug '05

09 Aug '05

I see mock and plague being a great way for third parties to do builds of their software on many distributions. For example, our customers commonly request Fedora, RHEL, SuSE, or SLES to be installed on their Beowulf clusters. There's common clustering software (dsh, mpich, torque, etc.) that we install on top of these OSes and I've been working on packaging most of these into rpms. Since mock/plague appear to be mostly Fedora centric, I've had to patch a few things to get it working. Attached is a patch that I created to deal with some SuSE deficiencies I've run across. Also attached is the buildroots file and mock config file. Bryan -- Aspen Systems, Inc. | http://www.aspsys.com/ Production Engineer | Phone: (303)431-4606 bryans(a)aspsys.com | Fax: (303)431-7196

1 0

Builds stuck in needsign/in-progress
by Bryan Stillwell 08 Aug '05

08 Aug '05

Every once in a while on my internal plague server I get builds that get stuck in the state "needsign/in-progress" and never make it into "needsign/success". Has anyone else run into this problem? Bryan -- Aspen Systems, Inc. | http://www.aspsys.com/ Production Engineer | Phone: (303)431-4606 bryans(a)aspsys.com | Fax: (303)431-7196

2 2

Killed jobs 'finished' not 'killed'?
by Bryan Stillwell 08 Aug '05

08 Aug '05

I've run into another problem with my internal plague server. It appears that when you run `plague-client kill jobid` it sets the status to 'finished' and not 'killed'. I believe the proper behaviour should be 'killed', but because its currently using 'finished' the `plague-client requeue jobid` command doesn't work and gives this message: Error: Job 11 must be either 'failed' or 'killed' to requeue. Bryan -- Aspen Systems, Inc. | http://www.aspsys.com/ Production Engineer | Phone: (303)431-4606 bryans(a)aspsys.com | Fax: (303)431-7196

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys August 2005