Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Ganymede/Build"
(→Syntax and Semantics) |
m (→Explanation: add update site URLs) |
||
Line 10: | Line 10: | ||
Of course, there really is no "build" of Ganymede, but only a copying of what is already available on each project's update site, to a central site. | Of course, there really is no "build" of Ganymede, but only a copying of what is already available on each project's update site, to a central site. | ||
+ | |||
+ | This central update site, naturally, is http://download.eclipse.org/releases/ganymede/. To get a sneak peek, point your Update Manager at http://download.eclipse.org/releases/ganymede/staging/. | ||
==The Projects' Roles== | ==The Projects' Roles== |
Revision as of 16:52, 15 December 2007
This page is related to the Ganymede Simultaneous Release.
Contents
Explanation
The Ganymatic is live and running every day. The status & logs are here: http://build.eclipse.org/ganymede/
In addition to sending emails to project release engineers who are responsible for broken builds, there are three 'Eclipse Build' format RSS feeds available for project teams to monitor. More info on feeds: Getting Started Guide, Feed Schema.
Of course, there really is no "build" of Ganymede, but only a copying of what is already available on each project's update site, to a central site.
This central update site, naturally, is http://download.eclipse.org/releases/ganymede/. To get a sneak peek, point your Update Manager at http://download.eclipse.org/releases/ganymede/staging/.
The Projects' Roles
Pre-Project Configuration Files
The pre-project configuration files are stored in the Callisto CVS:
:extssh:<your-committer-id-goes-here>@dev.eclipse.org:/cvsroot/callisto
Or, general "read" access via
:pserver:anonymous@dev.eclipse.org:/cvsroot/callisto
There is one project:
org.eclipse.ganymede.sitecontributions
Syntax and Semantics
<?xml version='1.0'?> <sc:siteContribution xmlns="http://www.eclipse.org/buckminster/CSpec-1.0" xmlns:sc="http://www.eclipse.org/buckminster/SiteContribution-1.0" rmapProviderURL="${downloads}/webtools/milestones/site.xml"> <sc:member name="Bjorn Freeman-Benson" email="bjorn.freeman-benson@eclipse.org" /> <sc:member name="Karl Matthias" email="webmaster@eclipse.org" /> <sc:cspec name="org.eclipse.wtp-sc"> <dependencies> <dependency name="org.eclipse.jpt.feature" versionDesignator="[1.0.0.v200706250000-77--CYQCCz-CoRPCCCH]" /> <dependency name="org.eclipse.jst" versionDesignator="[2.0.0.v200706110805-7B-18dDQISlz0z0cc-oasolrW8jP]" /> <dependency name="org.eclipse.wst.common_ui.feature" versionDesignator="[2.0.0.v200706041905-7C5EGzE9RvTVniSrwnf4TgOPe3e9]" /> </dependencies> <groups> <public name="Web and JEE Development"> <attribute component="org.eclipse.jst" /> <attribute component="org.eclipse.wst.common_ui.feature" /> </public> <public name="Other Development"> <attribute component="org.eclipse.jpt.feature" /> </public> </groups> </sc:cspec> </sc:siteContribution>
- ${downloads}/webtools/milestones/site.xml: The location of the project's update site. It's more efficient to access the site via a file path than a url, but a url will work. ${downloads} refers to the root of the http://download.eclipse.org/ server.
- Bjorn Freeman-Benson and bjorn.freeman-benson@eclipse.org: person to notify if this project is responsible for breaking the build. Feel free to have multiple people listed.
- org.eclipse.wtp-sc: the unique identifier for this site contribution
- org.eclipse.jpt.feature: The feature identifier. One per feature (of course). Features are listed one per <dependency .../> node.
- 2.0.0.v200706041905-7C5EGzE9RvTVniSrwnf4TgOPe3e9: The feature version. One per feature (of course). Buckminster (the technology Ganymatic is built on) has a number of ways to specify the version. Most projects will use a single fixed version here, although you can also have an empty string to mean "the latest version found on my update site".
- Web and JEE Development: Categories for the Ganymede site.xml file; used to group the features.
Schemas for these files are available at: http://www.eclipse.org/buckminster/schemas/siteContribution-1.0.xsd , http://www.eclipse.org/buckminster/schemas/cspec-1.0.xsd , http://www.eclipse.org/buckminster/schemas/common-1.0.xsd , http://www.eclipse.org/buckminster/schemas/rmap-1.0.xsd
Project Responsibilities
Each Ganymede project's PMC and/or Project Leader is responsible to keep its own *.sc (site contribution) file up to date as the project generates new milestones and release candidates. The project's project leader will probably delegate to the project's release engineer(s).
Obviously, each project's own update site must already exist (and be working) at the file location or url specified in the site contribution file.
Typically, as projects move from milestone to milestone (or release candidate to release candidate) only the version identifiers (e.g. 1.0.0.v200706250000-77--CYQCCz-CoRPCCCH]
) in the site contribution file will need to be changed. At other times, features might be added, removed, or renamed:
- Adding a feature: add new <dependency> and <attribute> nodes
- Removing a feature: remove the corresponding <dependency> and <attribute> nodes
- Renaming a feature: change the feature identifier (in two places) (e.g.,
org.eclipse.jpt.feature
).
TBD: how to trigger a new build and how to sign off that the project M-bits are ready to use.
The Central Ganymatic
As of 2007/10/14, the Ganymede builds are being run once a day at 11pm Eastern, 8pm Pacific, 5am Europe, 11am China.
TBD: how to trigger a new build and how to sign off that the project M-bits are ready to use.
Running Ganymatic On Your Machine
TBD
Additional Requirements and Information
See Europa Build for how last year's build worked.