23 Apr
2008
23 Apr
'08
08:50
Hi, > > http://code.google.com/soc/2008/suse/appinfo.html?csaid=DFC9A170A95499CD > > Nice to hear! :-) Yes, that's great :) > > Now I just want to gather users' expectations to this project. What > > would you like to see when using Build-Service in Eclipse? Thanks a > > lot! > > Here some use cases that come to my mind: > > - Add/Change packages I think Changing packages is a key thing. That means knowing the important file formats like tarballs, specs, dsc's etc. and offering editors for them, maybe on the fly checks on syntax etc. where applicable. - Create package source links > - Edit/Create package Templates Do you think about kind of "personal" Package Templates? Or general BS templates? If the latter, I don't think they should be really editable in Eclipse but somehow downloadable and available in the Eclipseclient on new package creation. However we do not have too much about templates yet, so this is not high priority. > - Add/Change projects Again here Editing as a key thing, similar to what I wrote about packages above. Additionally the client could assist for example on creating a metapackage as describecd for example on http://en.opensuse.org/Meta_Packages/ISV and other project specific things. - Create submit requests > - Edit/Create project Templates > - Add a "New Buildservice Package/Projekt" Workflow Again, these two seem to depend on templates. > - Edit specfiles and debian/* files using eclipse and upload them to the > buildservice automatically Directly after editing or on a "Sync with BS" command? > - could be achieved in using/integrating existing technology, e.g. > https://admin.fedoraproject.org/pkgdb/packages/name/eclipse-rpm-editor > - monitor build status Yes, important and can be quite eye-candy and thus a real benefit :) > - download (and maybe even deploy package(s)) Deploying is IMO a very interesting thing, we do not have that in other clients IMO. Can you elaborate a bit what is important there from a ISV s POV? > More advanced: > > - Add a new view similar to the CVS Browser to be able to browse > projects/packages on the buildservice and download them with rightclick Also Browsing by tags would be nice. > Btw.: on > http://code.google.com/soc/2008/suse/appinfo.html?csaid=DFC9A170A95499CD > you wrote, that the eclipse integration would depend on osc. I do not > think, that this would be a good approach. An eclipse plugin should work > out-of-the-box without installing additional software, IMHO. Agreed. OTOH osc evolves to be a cool python lib that eases client development a lot. But probably in the Eclipse case native Java is probably better. I hope there are enough usefull java tools to make that easy. > > For internal purposes I started writing a java client for the buildservice > to be able to upload, download and query the buildservice from within > ant-tasks, that are integrated into CruiseControl¹. > > Maybe we could combine our work and create a java client library for the > buildservice. Cool :) Klaas -- Klaas Freitag Architect OPS/IPD SUSE LINUX Products GmbH - Nuernberg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org