Hi Nicolas, Sorry for not responding earlier. Yes let's migrate all single builds to one big build. I won't have time to work on the paperwork for a Nebula-Restructuring until after EclipseCon.
Don can wait until we get this total build going, else let's setup the athena cron-build for xviewer and start migration to 1 Hudson Job afterwards. Tom Am 21.02.10 14:03, schrieb Nicolas Richeton: > Hi Tom, > > Before adding another build, I think we have to decide on how we are going to > build widgets in the future. > > Here is the current situation. > - All nebula projects, except Gallery are built on build.eclipse.org. > - Gallery is built on hudson. > > On build.eclipse.org : > Each project is built independently so we have 13 build jobs. There is no > trigger on CVS changes : all jobs are running once a day. There is also no > mail or warning on failure. > > On Hudson : > Gallery is building every 6 hours if there is a CVS change [1]. The last > time I played with Hudson configuration, I could only use a trigger on the > whole Nebula project. As soon as any widget changes, the Gallery is build. > This is because our repository layout is mixing all widgets' plugins at the > same level. > We also have the example project, which should be build on any change. > > Some month ago, I asked for the creation of new jobs in hudson in order to > convert all nebula builds to hudson [2]. But they were not created for the > good reason that 13 or more builds is quite a large number for a single > project and those projects would have build at the same time. > > So here is the question: > > Should we : > 1 - keep the current way of building (A project = 1 build) > 2 - create a single build for Nebula (1 build which will fail if one widget > fails to compile/test) > 3 - proceed with the nebula split into 2 sub projects : mature and > incubation, and build all mature projects together and incubation ones > separately. > > Since the current solution (1) is too resource-intensive, we should go to > solution 2 until we complete solution 3. > What do you think of this ? > > That said, I'll probably be able to set up the new build this week if we > decide to keep the current way of building. I also need to update the wiki > page on how to set up the build [3] > > I would also like to remind everyone that our project plan is not up to date > [4]. We should have at least commited/proposed/defered items based on > bugzilla queries for each widget. This is just a simple xml file on > eclipse.org cvs. Please take some time to add your widget bug queries. > I've set up a wiki page on this with explanations on how to update the > project plan file [5]. > > [1] > https://build.eclipse.org/hudson/job/cbi-nebula.widgets.gallery-0.5.x-nightly/ > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=285594 > [3] http://wiki.eclipse.org/Nebula_Releng > [4] > http://www.eclipse.org/projects/project-plan.php?projectid=technology.nebula > [5] http://wiki.eclipse.org/Nebula_Actions _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
