Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Ganymede/Build"

m (When The Gaymatic Runs)
Line 1: Line 1:
 
This page is related to the [[Ganymede Simultaneous Release]].
 
This page is related to the [[Ganymede Simultaneous Release]].
  
Information on the Gan-o-matic build system is under development.
+
==Explanation==
 +
The Ganymatic is being actively developed (this week). It is now running every day and the log is [http://build.eclipse.org/ganymede/]. I am working on converting all the project's Europa features-*.xml files into Ganymatic *.sc files.
  
* EMF would like Gan-o-matic to retrieve files from a different location than it uses to set up site.xml so that they can have a different url for the site.xml that does download tracking.
+
There are three RSS feeds in Nick's RSS format available for project teams to monitor: all Ganymede builds, all successful Ganymede builds, and all failed Ganymede builds.
:* If this means that we can use paths in our site*.xml files which contain absolute http:// paths instead of relative features/ paths, then yes. This is a request for EMF, MDT, M2T, and EMFT... and anyone who wants to track downloads from the Ganymede Update site as well as our own update sites. --[[User:Codeslave.ca.ibm.com|nickb]] 17:37, 21 September 2007 (EDT)
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=204272 bug 204272] requests that build results be notified by email.
+
* Build status reports will be available at http://build.eclipse.org/ganymede/ once I get it working. The reports will include:
+
** The most recent build
+
** The most recent successful build
+
** The N most recent builds
+
** The final builds for each of the milestones and release candidates
+
  
* See [[Europa Build]] for how last year's build worked.
 
 
==Explanation==
 
 
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. Plus, there is a "site.xml" file, and index.html, etc., that are authored, and Ganymede projects are (relatively) free to make updates to them.
 
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. Plus, there is a "site.xml" file, and index.html, etc., that are authored, and Ganymede projects are (relatively) free to make updates to them.
  
==Ganymatic Code==
+
==The Projects' Roles==
TBA
+
===Pre-Project Configuration Files===
 
+
==Per Project Configuration Files==
+
===Where===
+
 
The pre-project configuration files are stored in the Callisto CVS:
 
The pre-project configuration files are stored in the Callisto CVS:
  
Line 34: Line 22:
 
  org.eclipse.ganymede.sitecontributions
 
  org.eclipse.ganymede.sitecontributions
  
===Syntax and Semantics===
+
====Syntax and Semantics====
 +
''(Still under construction)''
 +
 
 
  <?xml version='1.0'?>
 
  <?xml version='1.0'?>
 
  <sc:siteContribution
 
  <sc:siteContribution
Line 66: Line 56:
 
# <font color="purple" style="font-weight: bold">Web and JEE Development</font>: Categories for the Ganymede site.xml file. These are used to group the features into categories.
 
# <font color="purple" style="font-weight: bold">Web and JEE Development</font>: Categories for the Ganymede site.xml file. These are used to group the features into categories.
  
===Responsibilities===
+
===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).
 
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).
  
Line 78: Line 68:
 
TBD: how to trigger a new build and how to sign off that the project M-bits are ready to use.
 
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.
  
==When The Ganymatic Runs==
+
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==
 +
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=204272 bug 204272] requests that build results be notified by email.
  
As of 2007/10/01, the Ganymede builds are still under development and are not being run at all.
+
See [[Europa Build]] for how last year's build worked.
  
 
[[Category:Ganymede]] [[Category:Coordinated]] [[Category:Releng]]
 
[[Category:Ganymede]] [[Category:Coordinated]] [[Category:Releng]]

Revision as of 08:25, 16 October 2007

This page is related to the Ganymede Simultaneous Release.

Explanation

The Ganymatic is being actively developed (this week). It is now running every day and the log is [1]. I am working on converting all the project's Europa features-*.xml files into Ganymatic *.sc files.

There are three RSS feeds in Nick's RSS format available for project teams to monitor: all Ganymede builds, all successful Ganymede builds, and all failed Ganymede builds.

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. Plus, there is a "site.xml" file, and index.html, etc., that are authored, and Ganymede projects are (relatively) free to make updates to them.

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

(Still under construction)

<?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:cspec name="org.eclipse.wtp">
      <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>
  1. ${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.
  2. org.eclipse.jpt.feature: The feature identifier. One per feature (of course). Features are listed one per <dependency .../> node.
  3. 2.0.0.v200706041905-7C5EGzE9RvTVniSrwnf4TgOPe3e9: The feature version. One per feature (of course).
  4. Web and JEE Development: Categories for the Ganymede site.xml file. These are used to group the features into categories.

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

  • bug 204272 requests that build results be notified by email.

See Europa Build for how last year's build worked.

Back to the top