[New: openFATE 308310] OBS - External workers / Project namespace dedicated
Feature added by: Dominique Leuenberger (dimstar)
Feature #308310, revision 1
Title: OBS - External workers / Project namespace dedicated
Buildservice: Unconfirmed
Priority
Requester: Important
Requested by: Dominique Leuenberger (dimstar)
Description:
OBS is a great platform but often the queues are long and it's difficult to schedule any timely 'release' of a package. The main issue is the available build power.
Suggest to allow for 'external' workers to connect (authenticated) to the BS and act as workers. Preferrably an authenticated worker should be allowed to pick up packages where the authenticated user has maintainer rights (this eliminates pretty much the 'danger' of injection of malicious binary results: the owner of the worker has full access to the repository anyhow).
Additionally it would be interesting if my 'worker farm' could be dedicated to one specific
Feature changed by: Sankar P (psankar)
Feature #308310, revision 2
Title: OBS - External workers / Project namespace dedicated
Buildservice: Unconfirmed
Priority
Requester: Important
Requested by: Dominique Leuenberger (dimstar)
Description:
OBS is a great platform but often the queues are long and it's
difficult to schedule any timely 'release' of a package. The main issue
is the available build power.
Suggest to allow for 'external' workers to connect (authenticated) to
the BS and act as workers. Preferrably an authenticated worker should
be allowed to pick up packages where the authenticated user has
maintainer rights (this eliminates pretty much the 'danger' of
injection of malicious binary results: the owner of the worker has full
access to the repository anyhow).
Additionally it would be interesting if my 'worker farm' could be
dedicated to one specific
Feature changed by: Per Jessen (pjessen)
Feature #308310, revision 4
Title: OBS - External workers / Project namespace dedicated
Buildservice: Unconfirmed
Priority
Requester: Important
Requested by: Dominique Leuenberger (dimstar)
Description:
OBS is a great platform but often the queues are long and it's
difficult to schedule any timely 'release' of a package. The main issue
is the available build power.
Suggest to allow for 'external' workers to connect (authenticated) to
the BS and act as workers. Preferrably an authenticated worker should
be allowed to pick up packages where the authenticated user has
maintainer rights (this eliminates pretty much the 'danger' of
injection of malicious binary results: the owner of the worker has full
access to the repository anyhow).
Additionally it would be interesting if my 'worker farm' could be
dedicated to one specific
Feature changed by: Adrian Schröter (adrianSuSE)
Feature #308310, revision 6
Title: OBS - External workers / Project namespace dedicated
- Buildservice: Unconfirmed
+ Buildservice: Rejected by (adrianSuSE)
+ reject date: 2010-01-22 15:47:47
+ reject reason: This will not work, if plenty of workstations but always
+ small are provided. We would get different builds which differs (simply
+ due to the different hardware) this means also we can not compare
+ multiple builds so we can trust the build results at all.
+ We can't even not allow this for own projects, because it would lead to
+ the situation that you can't be sure that the sources for the binaries
+ are on the server.
+ We are however open for the situation when a larger amount of systems
+ is provided somewhere at one place and we can make a contract to build
+ the trust.
Priority
Requester: Important
Requested by: Dominique Leuenberger (dimstar)
Description:
OBS is a great platform but often the queues are long and it's
difficult to schedule any timely 'release' of a package. The main issue
is the available build power.
-
Suggest to allow for 'external' workers to connect (authenticated) to
the BS and act as workers. Preferrably an authenticated worker should
be allowed to pick up packages where the authenticated user has
maintainer rights (this eliminates pretty much the 'danger' of
injection of malicious binary results: the owner of the worker has full
access to the repository anyhow).
Additionally it would be interesting if my 'worker farm' could be
dedicated to one specific
participants (1)
-
fate_noreply@suse.de