Mailinglist Archive: opensuse-features (201 mails)

< Previous Next >
[openFATE 305931] Temporary Build Support (aka mbuild)
  • From: fate_noreply@xxxxxxx
  • Date: Mon, 6 Apr 2009 20:15:30 +0200 (CEST)
  • Message-id: <feature-305931-6@xxxxxxxxxxxxxx>
Feature changed by: Michal Marek (michal-m)
Feature #305931, revision 6
Title: Temporary Build Support (aka mbuild)

Buildservice: Evaluation
Requester: Important
Projectmanager: Important

Requested by: Adrian Schröter (adriansuse)

A temporary build support is wanted to obsolete what we currently have
internal as mbuild. A temporary Build should fullfill the following
* Upload of local sources without the need to create a project or package
namespace manually.
* Build as part of an existing project, without the need to have write
access there and without to modify it.
* Build results should be stored and downloadable for X time.
Afterwards they need to get removed automatically.
* Build via a new single-shot mechanism: Ignoring current
scheduled/building/blocked states of existing packages and do not
reschdule again afterwards
* Hermes notification on build finish.
* priorisation needs to be possible somehow (low prio on,
high prio on for example).

#1: Michal Marek (michal-m) (2009-03-02 10:25:07)
An important feature is also that the build should not get blocked by
build dependencies, but rather take whatever packages are there and
attempt to build. Lack of this is the reason why we still use mbuild
for the KOTD (kernel of the day).
Another thing: is it planned to be able to submit multiple source
packages as part of a "mbuild" job? It would be really cool to be able
to build also kernel-syms and some KMPs as part of the KOTD.

#2: Adrian Schröter (adriansuse) (2009-03-19 10:45:14)
Yes, added to the feature.

+ #3: Michal Marek (michal-m) (2009-04-06 20:13:00) (reply to #2)
+ And what about being able to submit multiple (interdependent) source
+ packages in one mbuild job?

openSUSE Feature:

< Previous Next >
This Thread
  • No further messages