Home_greyopenFATE - openSUSE feature tracking > #305931
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Temporary Build Support (aka mbuild)

Feature state

Buildservice
Marketplace

Description

A temporary build support is wanted to obsolete what we currently have internal as mbuild.
A temporary Build should fullfill the following requirements:

  • 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 opensuse.org, high prio on build.suse.de for example).

Discussion


icons/user_comment.png M. M. wrote: (9 years ago)

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.

icons/user_comment.png A. S. wrote: (9 years ago)

Yes, added to the feature.

icons/user_comment.png M. M. wrote: (9 years ago)

And what about being able to submit multiple (interdependent) source packages in one mbuild job?

Last change: 5 years ago
Voting
Score: 2
  • Negative: 0
  • Neutral: 0
  • Positive: 2
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint