[opensuse-buildservice] Upstream integration
Hi, during summer of code I wrote part of upstream integration for the BS it works by parsing _upstream file located in package directory _upstream looks like this: <upstream> <source> <file archive='tar' compress='gzip'>mytarball.tgz</file> <svn> <destdir>common</destdir> <url>https://server/path</url> </svn> <exclude>somefile</exclude> <exclude>anotherfile</exclude> </source> <source> <file archive='tar' compress='gzip'>myothertarball.tgz</file> <cvs> <cvsroot>cvs.example.com</cvsroot> <path>abc/def</path> <user>someuser</user> <password>pass</password> <branch>REL_1_0</branch> </cvs> </source> </upstream> The question is - where to integrate this? I propose adding path in api, something like GET /source/<project>/<package>/make_upstream or may be better to POST /source/<project>/<package>?cmd=fetchUpstreamSource or make a new controller GET /upstream/<project>/<package>/fetch What you think of it? -- Regards ^^MAg^^ mailto:/jid: mag@entropy.be --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 13 February 2007 09:40, Rafal Kwasny wrote:
POST /source/<project>/<package>?cmd=fetchUpstreamSource
I like this best. This fits with the other commands we have. As the fetching of upstream sources can take a while, we need to do this asynchronously and also provide a way to report the status. A generic way to report the status, would be GET /status/<project>/<package>?cmd=fetchUpstreamSource What do you think? -- Cornelius Schumacher <cschum@suse.de> --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Cornelius Schumacher
-
Rafal Kwasny