[opensuse-buildservice] OSC upstream integration

Hi, currently I am working on upstream integration in BuildService. I have first patch for OSC. If you want to, you can take a look. If you have any related ideas, feel free to reply. For make this totally work, we also need to extend server backend of buildservice... I am thinking about some special "upstream scheduler" which have information about all _upstream files and trying "svn co" (or offcourse similar command for other supported SCM) which are compared with previous release numbers (stored "somewhere" :-) ) and if they are different new tarball are created and changes are commited. Do you have better idea how solve this problem? Yaloki: This can be also used for our following OBS migration, because upstream integration support http downloads too... :-) -- S pozdravem / Best regards Marek Stopka Official openSUSE community member Kontakty / Contacts Mobil/Cell phone: 774 59 79 40 E-mail: mstopka@opensuse.org WEB: www.m4r3k.org

2008/8/25 Marek Stopka (M4r3k) <marekstopka@gmail.com>:
Hi, currently I am working on upstream integration in BuildService. I have first patch for OSC. If you want to, you can take a look. If you have any related ideas, feel free to reply.
For make this totally work, we also need to extend server backend of buildservice... I am thinking about some special "upstream scheduler" which have information about all _upstream files and trying "svn co" (or offcourse similar command for other supported SCM) which are compared with previous release numbers (stored "somewhere" :-) ) and if they are different new tarball are created and changes are commited. Do you have better idea how solve this problem?
Yaloki: This can be also used for our following OBS migration, because upstream integration support http downloads too... :-) This will change the way on how work the opensuse API, Clients will need to change ?
-- S pozdravem / Best regards Marek Stopka Official openSUSE community member Kontakty / Contacts Mobil/Cell phone: 774 59 79 40 E-mail: mstopka@opensuse.org WEB: www.m4r3k.org
-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- If one day one reproaches you that your work is not a work of professional, say you that: Amateurs built the arch of Noah, and professionals the Titanic. --------------------------------------------------------------------------- Few people are done for independence, it is the privilege of the powerful ones. --------------------------------------------------------------------------- No key was wounded during the drafting of this message. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 2008-08-25 15:59:01 +0200, Marek Stopka (M4r3k) wrote:
Hi, currently I am working on upstream integration in BuildService. I have first patch for OSC. If you want to, you can take a look. If you have any related ideas, feel free to reply.
For make this totally work, we also need to extend server backend of buildservice... I am thinking about some special "upstream scheduler" which have information about all _upstream files and trying "svn co" (or offcourse similar command for other supported SCM) which are compared with previous release numbers (stored "somewhere" :-) ) and if they are different new tarball are created and changes are commited. Do you have better idea how solve this problem?
I don't know if the backend is the right place to implement this. For instance the official obs backend has no access to the internet and therefore it won't be possible to checkout the sources from the net. Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Marcus Hüwe
-
Marek Stopka (M4r3k)
-
Petit Eric