Mailinglist Archive: opensuse-buildservice (311 mails)

< Previous Next >
[opensuse-buildservice] Build Team Meeting
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Tue, 24 Nov 2009 13:29:48 +0100
  • Message-id: <200911241329.49060.adrian@xxxxxxx>

Present: freitag, cwh, mls, adrian, coolo


* Status round
* libxml for api and webclient ?
* 1.7 release
* svn move to gitorious and berlios

Status round:

* Working on http status delivery for hermes module.

* Installed own OBS instance for working on driver build support in kiwi.

* coolo branch is git now to make merging easy.
* moved server_status / monitor page to trunk.
* Worked on speedup of active xml, trying to switch from REXML to libxml.
Speedup of factor 10, but currently too many places which depend on REXML.
* analyzing frontend logs to speed up.
* Introduced project status as generic base for factory status page.
=> Collecting source or verify md5, devel package status and further items.
These get cached to be able to generate the status page fast.

* build03 XEN debugging, first Intel based worker in our farm

* Improved build log handling, coolo has implemented a "X last lines only"
web client for the web ui
* worked on scheduler support for clean product build support.
* indexed openSUSE:11.2* projects for

* Added Fedora 12 support together with mls.
* Added project wide submit request support in osc.
* Added request review mechanism.
=> complete, except for "superseded" funcationality in client.
* Added patchinfo support to api and osc.
=> missing final implementation to create the ID.

1.7 release:

To be done until 1.7 beta 1, target release date is within december:
* make new snapshot and fix new dependencies (esp. new ruby/rails modules)
* what dependson support in api and osc
* make repository status visible
* Final patchinfo support
* Attribute definition shall not be stored in project meta data anymore.
* DoD feature working again.

XML changes in api and webclient

REXML and activexml are not fast enough for real web browsing experience.
SmartXML is only used on software.o.o atm.

Coolo introduced a new rubyxml using libxml.

API has no performance problem with activexml, but webclient has. A
conversation from activexml to libxml is possible step by step. activesupport
has now libxml also, problem is that we might have problems to get our REST
interface working with it.

Call for testing of , to check if activexml
with libxml backend is working in all cases. So we can maybe switch for 1.7

svn move

The current plan is:

copy svn from forge to berlios project and remove OBS parts afterwards there.
OBS parts will be imported to own "openSUSE Build Service" module on
webclient -> rename webui
frontend -> rename to api
yabsc ?

We should do this step by step for each module. All modules will become an
own repository.
Everbody should create an gitorious account.

coolo will take care about import.
adrian will create a temporary solution for push mails.

AI: adrian&coolo write an anouncemout to all developers and anounce the point
of time when the new repositories will be used as default.


Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >