Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] MoDisco's dependencies

I can comment on the Orbit repositories. You are correct to use an "S-build" repository .... but, you do not need two of them. You only need the most recent one.

For more detail, in Orbit we impose a "-1" deadline on ourselves, to provide a "stable" repository approximately 1 week before the "0" deadline for a milestone or release. If anyone needs to use "warmups" before that S build (to get a newly added bundle, say) they can use an appropriate I-build until the S-build is ready, and then switch to the S-build URL once it becomes available. The changes in contents from a recent I-build to an S-build should be minimal, if any.  But, the idea is everyone uses the latest S-build for a milestone ... so that way there is no unnecessary duplication of "slightly old" bundles.

HTH




From:        Grégoire Dupé <gdupe@xxxxxxxxxxxxxxxx>
To:        cross-project-issues-dev@xxxxxxxxxxx
Date:        01/06/2011 02:33 PM
Subject:        [cross-project-issues-dev] MoDisco's dependencies
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx




Hello,

I’m one of the committers of MoDisco.

The build of MoDisco depends of the following projects: Birt, CDO, Datatools, EMF Compare, EMF, EMF Query, EMF Validation, M2M ATL, M2M QVT OML, Acceleo, Jet, MDT OCL, MDT UML2 Tools, Mylyn (WikiText), TMF Xtext, Orbit, Eclipse (EP).

And as MoDisco is in the release train, we need to build with the right version of each project. To check that and to avoid getting problems only the day of the milestone build, we have connected our nightly build on the following update sites:

Birt:
http://download.eclipse.org/birt/update-site/4.0-interim/
CDO:
http://download.eclipse.org/modeling/emf/cdo/updates/4.0-milestones
Datatools:
http://download.eclipse.org/datatools/downloads/drops/M_updates_1.9
EMF Compare:
http://download.eclipse.org/modeling/emf/compare/updates/interim/1.1/
EMF:
http://download.eclipse.org/modeling/emf/emf/updates/2.7milestones
EMF Query, EMF Validation:
http://download.eclipse.org/modeling/emf/updates/milestones/
M2M ATL:
http://download.eclipse.org/modeling/m2m/atl/updates/milestones/3.2/
M2M QVT OML:
http://download.eclipse.org/modeling/m2m/qvtoml/updates/3.1.0/milestones/
Acceleo:
http://download.eclipse.org/modeling/m2t/acceleo/updates/milestones/3.1
Jet:
http://download.eclipse.org/modeling/m2t/updates/releases/
MDT OCL:
http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/3.1.0
MDT UML2 Tools:
http://download.eclipse.org/modeling/mdt/updates/milestones/
Mylyn (WikiText):
http://download.eclipse.org/tools/mylyn/update/indigo/staging
TMF Xtext:
http://download.eclipse.org/modeling/tmf/updates/
Orbit:
http://download.eclipse.org/tools/orbit/downloads/drops/S20101014084557/repository/
     
http://download.eclipse.org/tools/orbit/downloads/drops/S20101204061544/repository/
Eclipse (EP):
http://download.eclipse.org/eclipse/updates/3.7milestones/S-3.7M4-201012081300

We suppose that those update sites always contain up-to-date versions of the needed projects, in order to detect build issues far before the milestone build weeks. Can the releng engineers confirm us that we pick up the right ones?

Thanks in advance,
Gregoire Dupe

_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top