[opensuse-buildservice] Build Team Meeting
present: bg, aj, mmaier, adrian, mls, cwh, tschmidt Topics ====== * Status round * gitourius switch * Commercial Support Evaluation * openSUSE.org server status Status round ============ * mls - bugfixing in scheduler SAT code, improved the speed a lot and removed the bottle neck. Current bottle neck are missing build power and a more clever dispatcher. Coolo wants to work on improved dispatcher which prefers projects which are more often downloaded and also packages and projects with source changes should be prefered. - rpm and deb binary caching in the worker code implemented and deployed. Works good, but broke kiwi image building, will be fixed today. * cwh - Try to fix kiwi problems for openSUSE 11.2, found problems in OBS code while doing this, which are solved meanwhile. kiwi from openSUSE 11.2 seems to have fundamental problems with the KIWICollect module atm. * mmaier - Moved all build hosts in our server rooms, solving power connection problems. * tschmidt - worked on software.o.o, bugfixes and ported to rails 2.3.4. - cleanup api server code together with mrueckert. - Thought about better deployment methods, digged capistrano * adrian - digged into attribute code of frontend, writing missing schemas and try to get this running for openSUSE 11.2 maintenance workflow. Gitorious switch ================ General consense is that we want to go to gitorious from svn (even though we are a bit frightend of git). The suggestion from Luke to reorganize the directory structure makes very much sense, we will do so after the move. We should sync this move also with the new deployment method of our servers as suggested by Thomas. Remaining concern: gitorious has no commit mails yet, this might be a blocking issue. Commercial Support Evaluation for OBS ===================================== Novell evaluates the options for a commercial support offering atm. Interessted parties should get into contact with Andreas Jaeger <aj@suse.de> who is driving this. Our support wiki page has been updated to reflect this: http://en.opensuse.org/Build_Service/Support openSUSE.org Server Status ========================== * Timeout and frontend issues are solved by replacing the hardware switch. Makes the builds also reliable again. * All build hosts are using the new binary cache code from Michael since today. * PowerPC build host is down atm, but WIP * We have currently 1 build1X host and 5 build2X hosts offline due to hardware problems. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 10/13/2009 11:38 AM, Adrian Schröter wrote:
Remaining concern: gitorious has no commit mails yet, this might be a blocking issue.
Every repository has its own atom feed[1]. I guess it is a better solution for gitorious not to send millions of emails per day :-) If you really need commit emails and feed is not working for you, one can still write a service that watches the feed and sends notifications via email. [1] in format: http://gitorious.org/<project>/<repo>.atom e.g.: http://gitorious.org/opensuse/scout.atom -- Best Regards / S pozdravom, Pavol RUSNAK SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xA6917144 19000 Praha 9, CR prusnak[at]suse.cz http://www.suse.cz -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 13. Oktober 2009 13:14:19 schrieb Pavol Rusnak:
On 10/13/2009 11:38 AM, Adrian Schröter wrote:
Remaining concern: gitorious has no commit mails yet, this might be a blocking issue.
Every repository has its own atom feed[1]. I guess it is a better solution for gitorious not to send millions of emails per day :-) If you really need commit emails and feed is not working for you, one can still write a service that watches the feed and sends notifications via email.
well, I still would prefer optional mails in addition. They were very usefull in my personal working style so far, since I just need to switch between my work on my mail folder (what I need to do anyway), but not keep also always a browser with a certain page open. And it seems I am not alone with this. bye adrian
[1] in format: http://gitorious.org/<project>/<repo>.atom e.g.: http://gitorious.org/opensuse/scout.atom
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
Am Dienstag, 13. Oktober 2009 13:14:19 schrieb Pavol Rusnak:
On 10/13/2009 11:38 AM, Adrian Schröter wrote:
Remaining concern: gitorious has no commit mails yet, this might be a blocking issue.
Every repository has its own atom feed[1]. I guess it is a better solution for gitorious not to send millions of emails per day :-) If you really need commit emails and feed is not working for you, one can still write a service that watches the feed and sends notifications via email.
well, I still would prefer optional mails in addition. They were very usefull in my personal working style so far, since I just need to switch between my work on my mail folder (what I need to do anyway), but not keep also always a browser with a certain page open.
I agree. That atom feed is not useful for reviewing commits. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Pavol Rusnak wrote:
On 10/13/2009 11:38 AM, Adrian Schröter wrote:
Remaining concern: gitorious has no commit mails yet, this might be a blocking issue.
Every repository has its own atom feed[1]. I guess it is a better solution for gitorious not to send millions of emails per day :-) If you really need commit emails and feed is not working for you, one can still write a service that watches the feed and sends notifications via email.
[1] in format: http://gitorious.org/<project>/<repo>.atom e.g.: http://gitorious.org/opensuse/scout.atom
For me it would be a regression not to get commit mails with a full diff. Because I like to stay up to date which changes get committed to the code I'm working on. Greetings -- Thomas Schmidt (tschmidt [at] suse.de) SUSE Linux Products GmbH :: Research & Development :: Tools "Don't Panic", Douglas Adams (1952 - 11.05.2001) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Le mardi 13 octobre 2009, à 11:38 +0200, Adrian Schröter a écrit :
General consense is that we want to go to gitorious from svn (even though we are a bit frightend of git). The suggestion from Luke to reorganize the directory structure makes very much sense, we will do so after the move.
If you want to split out the code in different repositories, you can't do this after the move. Or, well, you can, but you'll lose the "small history" benefit: checking the code out will still have the whole history for everything. It's better to reorganize during the move, if possible. For example, it should be trivial to create a stand-alone git repo for osc with "git filter-branch --subdirectory-filter src/clientlib/python/osc/ -- --all" (which is an example from the filter-branch man page). Vincent -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (5)
-
Adrian Schröter -
Ludwig Nussel -
Pavol Rusnak -
Thomas Schmidt -
Vincent Untz