[openFATE 306471] auto create torrent files for images created
Feature added by: Jigish Gohil (cyberorg) Feature #306471, revision 1, last change by Title: auto create torrent files for images created Buildservice: Unconfirmed Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: Currently only metalink is created for the images created on the build service, it would be nice to have torrent files created too at the time of publishing the images. -- openSUSE Feature: https://features.opensuse.org/306471
Feature changed by: Andreas Jaeger (a_jaeger) Feature #306471, revision 3 - Title: auto create torrent files for images created + Title: Auto create torrent files for images created - Buildservice: Unconfirmed + Buildservice: Evaluation Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: Currently only metalink is created for the images created on the build service, it would be nice to have torrent files created too at the time of publishing the images. -- openSUSE Feature: https://features.opensuse.org/306471
Feature changed by: Adrian Schröter (adrianSuSE) Feature #306471, revision 4 Title: Auto create torrent files for images created Buildservice: Evaluation Priority Requester: Important + Projectmanager: Neutral Requested by: Jigish Gohil (cyberorg) Description: Currently only metalink is created for the images created on the build service, it would be nice to have torrent files created too at the time of publishing the images. + Discussion: + #1: Adrian Schröter (adriansuse) (2009-10-29 08:38:26) + it easy to create torrent files, but who will seed them ? + I am very much against that we will do it via our line. + Lars, maybe a seed could setup automatically at widehat ? -- openSUSE Feature: https://features.opensuse.org/306471
Feature changed by: Wallacy Freitas (wallacyf) Feature #306471, revision 5 Title: Auto create torrent files for images created Buildservice: Evaluation Priority Requester: Important Projectmanager: Neutral Requested by: Jigish Gohil (cyberorg) Description: Currently only metalink is created for the images created on the build service, it would be nice to have torrent files created too at the time of publishing the images. Discussion: #1: Adrian Schröter (adriansuse) (2009-10-29 08:38:26) it easy to create torrent files, but who will seed them ? I am very much against that we will do it via our line. Lars, maybe a seed could setup automatically at widehat ? + #2: Wallacy Freitas (wallacyf) (2010-09-17 16:45:53) (reply to #1) + Just add the build server html download link as web seed. + Like burnbit.com + -- openSUSE Feature: https://features.opensuse.org/306471
Feature changed by: Lars Vogdt (lrupp) Feature #306471, revision 6 Title: Auto create torrent files for images created - Buildservice: Evaluation by engineering manager + Buildservice: Ready + Milestone: 3.0 Priority Requester: Important Projectmanager: Neutral Requested by: Jigish Gohil (cyberorg) Product Manager: (Novell) Project Manager: (Novell) Engineering Manager: (Novell) + Developer: (Novell) Partner organization: openSUSE.org Description: Currently only metalink is created for the images created on the build service, it would be nice to have torrent files created too at the time of publishing the images. + References: + packages: obs-server Discussion: #1: Adrian Schröter (adriansuse) (2009-10-29 08:38:26) it easy to create torrent files, but who will seed them ? I am very much against that we will do it via our line. Lars, maybe a seed could setup automatically at widehat ? #2: Wallacy Freitas (wallacyf) (2010-09-17 16:45:53) (reply to #1) Just add the build server html download link as web seed. Like burnbit.com - + #3: Lars Vogdt (lrupp) (2011-04-20 18:54:25) + IMHO there should be some configuration options to define some options. + What comes into my mind as example: + * comment + * target + * tracker + e might set some "auto-values" based on best guess after the build if + there's nothing configured - but first I like to see those options + storable in the OBS. -- openSUSE Feature: https://features.opensuse.org/306471
participants (1)
-
fate_noreply＠suse.de