buildsys April 2013

buildsys@lists.fedoraproject.org

6 participants
5 discussions

[koji PATCH] allow setting the timeout for builds from config file
by Dan Horák 09 Dec '13

09 Dec '13

--- builder/kojid | 5 +++-- builder/kojid.conf | 3 +++ koji/__init__.py | 2 +- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/builder/kojid b/builder/kojid index f906d0b..18c1fa4 100755 --- a/builder/kojid +++ b/builder/kojid @@ -204,7 +204,7 @@ class BuildRoot(object): for k in ('repoid', 'tag_name'): if hasattr(self, k): opts[k] = getattr(self, k) - for k in ('mockdir', 'topdir', 'topurl', 'topurls', 'packager', 'vendor', 'distribution', 'mockhost', 'yum_proxy'): + for k in ('mockdir', 'topdir', 'topurl', 'topurls', 'packager', 'vendor', 'distribution', 'mockhost', 'yum_proxy', 'rpmbuild_timeout'): if hasattr(self.options, k): opts[k] = getattr(self.options, k) opts['buildroot_id'] = self.id @@ -3060,6 +3060,7 @@ def get_options(): 'maven_repo_ignore': '*.md5 *.sha1 maven-metadata*.xml _maven.repositories ' 'resolver-status.properties *.lastUpdated', 'failed_buildroot_lifetime' : 3600 * 4, + 'rpmbuild_timeout' : 3600 * 24, 'cert': '/etc/kojid/client.crt', 'ca': '/etc/kojid/clientca.crt', 'serverca': '/etc/kojid/serverca.crt'} @@ -3067,7 +3068,7 @@ def get_options(): for name, value in config.items('kojid'): if name in ['sleeptime', 'maxjobs', 'minspace', 'retry_interval', 'max_retries', 'offline_retry_interval', 'failed_buildroot_lifetime', - 'timeout',]: + 'timeout', 'rpmbuild_timeout',]: try: defaults[name] = int(value) except ValueError: diff --git a/builder/kojid.conf b/builder/kojid.conf index 1fa9ad4..05fe3b0 100644 --- a/builder/kojid.conf +++ b/builder/kojid.conf @@ -32,6 +32,9 @@ ; The _host string to use in mock ; mockhost=koji-linux-gnu +; Timeout for build duration (24 hours) +; rpmbuild_timeout=86400 + ; The URL for the xmlrpc server server=http://hub.example.com/kojihub diff --git a/koji/__init__.py b/koji/__init__.py index f42226b..8ab81a8 100644 --- a/koji/__init__.py +++ b/koji/__init__.py @@ -1266,7 +1266,7 @@ def genMockConfig(name, arch, managed=False, repoid=None, tag_name=None, **opts) # don't encourage network access from the chroot 'use_host_resolv': opts.get('use_host_resolv', False), # Don't let a build last more than 24 hours - 'rpmbuild_timeout': 86400 + 'rpmbuild_timeout': opts.get('rpmbuild_timeout', 86400) } # bind_opts are used to mount parts (or all of) /dev if needed. -- 1.7.7.6

2 1

Koji-1.7.1-1.fc17 repository toplink failure
by Anthony Joseph Messina 03 Jul '13

03 Jul '13

After upgrading to koji-1.7.1 on my private hub and builders, my builders are no longer able to use the repositories they create when building subsequent dependent packages. When attempting to install locally built packages, the following error is issued in the root.log: error was [Errno 2] Local file does not exist: /tmp/koji/tasks/9129/19129/repo_3627_premerge/toplink/packages/... The repos are created successfully: $ /usr/bin/createrepo -vd -o /tmp/koji/tasks/9129/19129/repo -i /mnt/koji/repos/f17-build/3627/x86_64/pkglist -g /mnt/koji/repos/f17- build/3627/groups/comps.xml --update --skip-stat /mnt/koji/repos/f17- build/3627/x86_64 Scanning old repo data Spawning worker 0 with 36 pkgs Worker 0: reading toplink/packages/dahdi-tools/2.6.1/3.fc17.1/x86_64/dahdi- tools-2.6.1-3.fc17.1.x86_64.rpm Worker 0: reading toplink/packages/dahdi-tools/2.6.1/3.fc17.1/x86_64/dahdi- tools-devel-2.6.1-3.fc17.1.x86_64.rpm Worker 0: reading toplink/packages/dahdi-tools/2.6.1/3.fc17.1/x86_64/dahdi- tools-libs-2.6.1-3.fc17.1.x86_64.rpm ... ... I believe the issue is related to the following commit: https://fedorahosted.org/koji/changeset/da6dd0b1832e9929565a1ab03ab844aaced… I'm not sure why when building packages, the builders are inserting '/tmp/koji/tasks/9129/19129/repo_3627_premerge/toplink' instead of topdir or topurl, such as '/mnt/koji' or 'http://example.com/kojifiles' Right now I'm working on selectively reverting that commit to see if I can build packages against other local packages. Any assistance is appreciated. Thanks. -Anthony -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

4 13

Cannot build RHEL5/F18 packages on Fedora 18
by Michael Cronenworth 03 Apr '13

03 Apr '13

I had to build my first RHEL5 and F18 packages today after upgrading my Koji server from Fedora 17 to 18. I cannot build RHEL5 or F18 packages, but RHEL6 packages compile fine. All packages built successfully under Fedora 17. RHEL5 root.log: [snip] DEBUG util.py:264: error reading information on service rdisc: Cannot allocate memory DEBUG util.py:264: warning: %post(iputils-20020927-46.el5.i386) scriptlet failed, exit status 1 DEBUG util.py:264: Non-fatal POSTIN scriptlet failure in rpm package iputils-20020927-46.el5.i386 DEBUG util.py:264: error reading information on service iscsid: Cannot allocate memory DEBUG util.py:264: error reading information on service iscsi: Cannot allocate memory DEBUG util.py:264: warning: %post(iscsi-initiator-utils-6.2.0.872-6.el5.i386) scriptlet failed, exit status 1 DEBUG util.py:264: Non-fatal POSTIN scriptlet failure in rpm package iscsi-initiator-utils-6.2.0.872-6.el5.i386 RHEL5 build.log: [snip] gcc: error trying to exec 'cc1': execvp: No such file or directory F18 build.log: [snip] collect2: fatal error: cannot find 'ld' Is F18's mock broken? Michael

3 8

koji-1.8.0
by Mike McLean 02 Apr '13

02 Apr '13

Koji 1.8.0 is tagged and posted. The big change in 1.8 is a refactor of how images (livecd, appliance) are stored in the database and on disk. Previously they lived in their own space. Now they are treated on par with other builds. * Mon Apr 1 2013 Mike McLean <mikem at redhat.com> - 1.8.0-1 - refactor how images are stored and tracked (images as builds) - delete repos in background - limit concurrent maven regens - let kojira delete repos for deleted tags - check for a target before waiting on a repo - don't append to artifact_relpaths twice in the case of Maven builds - Use standard locations for maven settings and local repository - Specify altDeploymentRepository for Maven in settings.xml NOT on command line - rather than linking to each artifact from the Maven repo, link the version directory - handle volumes in maven repos - fix integer overflow issue in checkUpload handler - koji-shadow adjustments - change default ssl timeout to 60 seconds - rewrite ensuredir function to avoid os.makedirs race - rename -pkg commands to -build - implement remove-pkg for the cli - a little more room to edit host comments - use wsgi.url_scheme instead of HTTPS - handle relative-to-koji urls in mergerepos

3 2

revisor move repodata
by Grzegorz Dwornicki 01 Apr '13

01 Apr '13

Hi I am making my own respin of install ISO. I have problem with revisor... It makes the installer and it is launching. But when it wants to look in repository on DVD. It gives me error about repmod.xml. It looks in directory with RPMs in it but repodata dir is on main directory of DVD. How can I make revisor move it into directory with RPMs? Greg.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys April 2013