Mailinglist Archive: opensuse-buildservice (239 mails)

< Previous Next >
[opensuse-buildservice] Build Service Status
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Tue, 20 May 2008 13:06:47 +0200
  • Message-id: <200805201306.49129.adrian@xxxxxxx>

present: freitag, mjung, jcborn, tpatzig, froh, adrian, poeml, abauer

Status:
* general
* 1.0
- devel project implementation

General Status:
===============

freitag:
* Hermes support Jabber notifications now
* Bugfixing and Documentation work for Hermes
* Open question is if we want to run an own jabber server or
to use existing ones.
* Will be on LinuxTag next week.

mjung:
* Thinking about how to implement the trust handling. One single
global trust seems to have some short commings, an individual
trust to certain persons might be the way to go.
Looking for specialised documentation around these topics
and discusses with different people in house.
* Will be on LinuxTag next week.

jcborn:
* Created installation isos with kiwi. YaST does start up, but
YaST has some problems. Most likely due to missing incorrect
repository setup. Need to debug esp. multiarch setup problems.

tpatzig:
* Worked on Starship, support for comments for types.
* Implemented a filter for project results in osc.

abauer:
* Updated api.opensuse.org to current svn
-> support for devel project
-> branch request call
* Fixing several bugzilla reports.

adrian:
* created scripts to write "devel project" definition to all
packages in openSUSE:Factory. They run still in dry mode.
* Debugged build host issues, switched all build systems to use
LVM and switched off a number of build hosts which have currently
problems.
* Current backend server is at it's end (was running into swaping out
schedulers, which decreased the speed a lot). We have already a new
system, which was unstable in the past, but seems to run stable
after firmware uprade. This should solve this.

poeml:
* released new osc package. Details are on
http://en.opensuse.org/Build_Service/News

1.0 Status:
===========

devel project handling:
* Discussion to implement an api call to allow devel project change in
foreign projects. This need a permission check, allowing it only, if the
devel project points a project with write access for the user.
* The (web/osc) client needs to check before branch, if devel project exists
and report this to the user. The client should have a option to ignore the
devel project setting.
* look up for devel project on branch should get implemented in the API and
not in the clients.

AI: freitag define api branch call to follow devel project definition
and how to ignore to follow the devel project.

AI: adrian define used xml fields and create submission workflow in
documentation.



--

Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx

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

< Previous Next >
This Thread
  • No further messages