[openFATE 305931] Temporary Build Support (aka mbuild)
Feature added by: Adrian Schröter (adrianSuSE) Feature #305931, revision 1, last change by Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) 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. -- openSUSE Feature: https://features.opensuse.org/305931
Feature changed by: Michal Marek (michal-m) Feature #305931, revision 2 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) 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. + Discussion: + #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. -- openSUSE Feature: https://features.opensuse.org/305931
Feature changed by: Adrian Schröter (adrianSuSE) Feature #305931, revision 3 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) 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. Discussion: #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. -- openSUSE Feature: https://features.opensuse.org/305931
Feature changed by: Adrian Schröter (adrianSuSE) Feature #305931, revision 4 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) 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. Discussion: #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. -- openSUSE Feature: https://features.opensuse.org/305931
Feature changed by: Adrian Schröter (adrianSuSE) Feature #305931, revision 5 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) 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: #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. -- openSUSE Feature: https://features.opensuse.org/305931
Feature changed by: Michal Marek (michal-m) Feature #305931, revision 6 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) 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: #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: https://features.opensuse.org/305931
Feature changed by: Lars Vogdt (lrupp) Feature #305931, revision 12 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation by engineering manager Priority Requester: Important Projectmanager: Important Info Provider: (Novell) Requested by: Adrian Schröter (adriansuse) Project Manager: (Novell) Engineering Manager: (Novell) Developer: (Novell) - Developer: (Novell) Developer: Peter Poeml (poeml) Partner organization: openSUSE.org 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: #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: https://features.opensuse.org/305931
Feature changed by: Libor Pechacek (LPechacek) Feature #305931, revision 15 Title: Temporary Build Support (aka mbuild) Buildservice: Evaluation by engineering manager Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) - Developer: Peter Poeml (poeml) Partner organization: openSUSE.org 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: #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: https://features.opensuse.org/305931
participants (1)
-
fate_noreply@suse.de