[Bug 701972] New: Creating a Tag by OSC is too slow what induce a risk of error
https://bugzilla.novell.com/show_bug.cgi?id=701972 https://bugzilla.novell.com/show_bug.cgi?id=701972#c0 Summary: Creating a Tag by OSC is too slow what induce a risk of error Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: All URL: http://wiki.meego.com/File:ObsTagCopy.tgz OS/Version: Linux Status: NEW Keywords: build, dogfood, Functionality Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: mrueckert@novell.com ReportedBy: dominig.arfoll@fridu.net QAContact: adrian@novell.com Found By: Community User Blocker: No Hi, In the MeeGo TV project we are using OBS to deliver the open source code to our users. They then integrate that open source code with their proprietary code (often drivers and applications) In order to enable them to collect a known working release of a set of packages we need to create a snap shot. Creating a snap shot by a branch is long and tedious and so we have created the concept of Tag (like in svn). The Tag is a a list of packages with MD5 from a project. That tag can be used to automatically copy the associated packages from the public OBS to a private OBS instance. An obs2obscopy tool only copy the packages which are not already present and at the correct revision on the target. The main issue comes from the fact that we create the Tag with a set of osc log command which takes time (about 10mn for MeeGo oss 1.2 which has about 1300 packages) and the risk of someone changing a package during that time is not negligible. For info the source of the obstag and obs2obscopy tools are attached with this bug and the latest version can be found here : http://wiki.meego.com/File:ObsTagCopy.tgz Proposition ======= Tag Creation ----------- What would be very useful would be for OBS to directly allow the creation of such a Tag via an API command. As the information is already present in the DB it would be quick and the risk of change happening during the tag creation could be eliminated. It would also reduce the load of the OBS server compared to the current method which run more than a thousand osc log requests to create a Tag. Copy from Tag ------------- What would be then nice to have, would be the integration of the obs2obscopy to the API as it would reduce the load on OBS and simplify the use of the Tag to users. That second requirement is more a nice to have as the current tool does its job. -- Dominig ar Foll MeeGo TV Intel Open Source Technology Centre. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701972 https://bugzilla.novell.com/show_bug.cgi?id=701972#c Marcus Rückert <mrueckert@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|mrueckert@suse.com |speilicke@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=701972 https://bugzilla.novell.com/show_bug.cgi?id=701972#c1 Sascha Peilicke <speilicke@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |INVALID --- Comment #1 from Sascha Peilicke <speilicke@suse.com> 2011-11-14 14:08:49 UTC --- Is this supposed to be a feature request? You want a stable set of packages, something that we would call a distribution release. http://en.opensuse.org/openSUSE:Factory_development_model What is meant by 'snapshot by branch'? What info do you get by parsing commit logs that isn't available elsewhere? I'm sorry, but this proposal doesn't make much sense IMO. A clear statement what you want to achieve and what information you need / is currently missing would help. Until then... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com