autoqa-devel

autoqa-devel@lists.fedorahosted.org

967 discussions

[AutoQA] #434: Depcheck incorrectly passes for soname changes
by fedora-badges 20 Nov '12

20 Nov '12

#434: Depcheck incorrectly passes for soname changes --------------------+---------------------- Reporter: kalev | Owner: Type: task | Status: new Priority: major | Milestone: Depcheck Component: core | Keywords: Blocked By: | Blocking: --------------------+---------------------- Depcheck should reject packages with soname bumps, when the dependant packages haven't all been rebuilt. See e.g. https://admin.fedoraproject.org/updates/FEDORA-2012-18509 : tagged in f18: {{{ geos-3.3.2-3.fc18, provides: libgeos-3.3.2.so()(64bit) player-3.0.2-20.fc18, requires: libgeos-3.3.2.so()(64bit) }}} the candidate builds: {{{ geos-3.3.6-1.fc18, provides: libgeos-3.3.6.so()(64bit) player-3.0.2-21.fc18, requires: libgeos-3.3.2.so()(64bit) }}} This above should fail depcheck, because player-3.0.2-21.fc18 hasn't been rebuilt for the new soname. However, the depcheck tests passed: - http://autoqa.fedoraproject.org/report/j0u9 (x86_64) - http://autoqa.fedoraproject.org/report/j0u5 (i386) -- Ticket URL: <https://fedorahosted.org/autoqa/ticket/434> AutoQA <http://autoqa.fedorahosted.org> Automated QA project

1 1

[fedora-build-service] #17: Replace return code based error handling by custom exception class
by fedora-badges 17 Nov '12

17 Nov '12

#17: Replace return code based error handling by custom exception class ----------------------------+---------------------- Reporter: amitksaha | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: Image Building | Version: Keywords: | ----------------------------+---------------------- The code uses return codes to detect and handle/report errors. This is not very easy to implement and track errors. Perhaps a custom exception class(es) can be used in place. -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/17> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 0

[fedora-build-service] #11: Support Triggers from fedbus
by fedora-badges 16 Nov '12

16 Nov '12

#11: Support Triggers from fedbus ----------------------------+----------------------------- Reporter: tflink | Owner: somebody Type: enhancement | Status: new Priority: minor | Milestone: Glorious Future Component: Job Management | Version: Keywords: | ----------------------------+----------------------------- Fedbus current emits messages for builds and updates. Support the monitoring of fedbus, looking for specific package builds. If there are new builds of the desired package, wait X minutes and kick off an ISO build job -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/11> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 2

Fedora Build Service: Configuration files and Options to support
by Amit Saha 15 Nov '12

15 Nov '12

Hi all, In its current state, the CLI tools require the user to strictly follow the supported templates and specify *all* the options and sections -- even if they are blank. Even for the Web UI, the config file is generated such that it follows this template strictly. That is not very exciting. [1a,1b] As a first step towards changing this to allow the config file to have only the bare minimum required for building images, I have created a list of the three tools used to create boot, DVD and live images with their mandatory, optional with no sensible defaults, optional with sensible defaults and switches. The list can be found at [2]. Please correct if there is anything I may have got wrong. Is it fair to assume that only the mandatory options as required by the original tools should also be the only ones supported by the build service as well? Once this list is decided, the CLI and the WebUI can assume the original sensible defaults or change them to a pre-decided default values for the others, in case they are not specified. [1a] https://fedorahosted.org/fedora-build-service/ [1b] https://fedorahosted.org/releases/f/e/fedora-build-service/devel/doc/HOWTO.… [2] https://gist.github.com/4076586 [2] I have plans for a config file generator script. Thanks for any inputs. Best, Amit. -- Amit Saha <http://echorand.me> Infrastructure Engineering and Development Red Hat, Inc.

1 0

[fedora-build-service] #15: Virtualenv Compatiblity and Instructions
by fedora-badges 14 Nov '12

14 Nov '12

#15: Virtualenv Compatiblity and Instructions -------------------------+----------------- Reporter: amitksaha | Owner: Type: enhancement | Status: new Priority: major | Milestone: Component: General | Version: Keywords: | -------------------------+----------------- Add instructions and test support for working on the project with virtualenv. -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/15> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 0

Current State of Image Building Project
by Tim Flink 13 Nov '12

13 Nov '12

I figure that one good place to start is to describe the current state of the project - what it can do and what the gotchas are. Amit, if I'm missing anything, please correct me or add what I'm missing. The local part of image building works fine - there are some quirks to the process and a configuration file format to learn but the added builds are downloaded and included in images. I haven't done much testing with building live images but I believe that is also working. In order to use any of the building code, you need to have the following installed: koji lorax livecd-tools pungi pykickstart spin-kickstarts Virtualenv doesn't work unless you create it as root because the CLIs need to be run as root for pungi/lorax and that changes paths to the point that not all the code works. I'm sure there are ways to work around it other than creating the virtualenv as root but I haven't tried very hard to find one. The remote parts work once set up - I had it set up at one point without the web front end and was able to build images. It needs a bit of polish but the needed stuff is mostly there, I just found the setup process to be a little touchy and fragile. The current method of configuration is rather pre-defined and not incredibly flexible but the basic method is sound. The web interface wasn't a priority during GSoC and thus, it is pretty rough around the edges. I was never able to get the full stack working but it's certainly capable of working. The UX needs more designing and a re-skin but this stuff can be done at a later date. I think that sums it up relatively well. The docs should fill in any more details that I've not written enough to start using the code. If not, feel free to ask questions here or in #fedora-qa. Tim

2 1

Image Building Project
by Tim Flink 13 Nov '12

13 Nov '12

We've been talking a little bit on an internal list (the conversation spawned out of something unrelated) about getting the image build service project from GSoC 2012 to the point where it can be deployed and used. Since the project doesn't have a mailing list of its own and it isn't all that unrelated to autoqa, we're moving the conversation here. I spent a little bit of time putting git and trac into a somewhat usable shape and filed a few tickets for some of the work that needs to be done. I'm going to continue doing so and would welcome any help in this department If anyone wants to be involved with the discussion and/or development, please let one of us know. We don't have a list set up but I'd love to get help on this - both Amit and I have admin access to the project and are able to add people. The trac instance is at: https://fedorahosted.org/fedora-build-service/ Git is at: http://git.fedorahosted.org/cgit/fedora-build-service.git/ I've pushed the current docs to: https://fedorahosted.org/releases/f/e/fedora-build-service/devel/doc/ Tim

1 1

[fedora-build-service] #13: Support intergration with blocker tracking app to spin new smoke builds
by fedora-badges 13 Nov '12

13 Nov '12

#13: Support intergration with blocker tracking app to spin new smoke builds ---------------------------+----------------------------- Reporter: tflink | Owner: somebody Type: enhancement | Status: new Priority: minor | Milestone: Glorious Future Component: Web Interface | Version: Keywords: | ---------------------------+----------------------------- One of things that QA's blocker tracking app was designed to do was to track the updates which are reported to have blocker-fixing updates in them. Update the web interface to support communicating with an instance of the blocker tracking app for identifying blocker and NTH fixing updates. Depends on the implementation of an API for the tracking app: https://fedorahosted.org/fedora-qa/ticket/323 -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/13> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 0

[fedora-build-service] #12: Reduce the number of Celery queues used for job control
by fedora-badges 13 Nov '12

13 Nov '12

#12: Reduce the number of Celery queues used for job control ----------------------------+------------------------------------ Reporter: tflink | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Semi-Public Deployment Component: Job Management | Version: Keywords: | ----------------------------+------------------------------------ At the moment, the build service requires one Celery queue per (version, arch) tuple supported in the builders. This doesn't scale well and makes rabbitmq admin a bit messier than it needs to be. Celery does support adding attributes to tasks on a queue and the last time I looked, celeryd can be configured to only take tasks with certain attributes. Change the queue setup such that there are fewer queues needed to support distributed building (down to one queue, if possible and it makes sense) -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/12> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 0

Re: [fedora-build-service] #6: Enhance Command Line Client UI (was: Ehance Command Line Client UI)
by fedora-badges 13 Nov '12

13 Nov '12

#6: Enhance Command Line Client UI -----------------------------+-------------------------------- Reporter: amitksaha | Owner: amitksaha Type: enhancement | Status: new Priority: major | Milestone: Initial Deployment Component: Image Building | Version: Resolution: | Keywords: -----------------------------+-------------------------------- Changes (by tflink): * component: General => Image Building * milestone: => Initial Deployment Comment: Fixing typo and assigning to milestone. This will need more detail but that will probably be after some discussion on a mailing list. For now, I'm putting this as 'initial deployment' but it could probably be put off until later. -- Ticket URL: <https://fedorahosted.org/fedora-build-service/ticket/6#comment:1> fedora-build-service <https://fedorahosted.org/fedora-build-service> A service to build fedora images with a somewhat arbitrary package set from the standard fedora repos or builds from koji.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

autoqa-devel