Jump to: navigation, search

Difference between revisions of "CDO/Release Engineering"

< CDO
(The Releng Component)
(The Releng Component)
Line 13: Line 13:
 
The remainder of this section lists some typical releng tasks that lead to modification of one or several of the files in the releng component. Here is an overview of how they relate to each other:
 
The remainder of this section lists some typical releng tasks that lead to modification of one or several of the files in the releng component. Here is an overview of how they relate to each other:
  
[[Image:releng-files.png|320px]]
+
[[Image:releng-files.png|640px]]
  
 
=== Adding dependencies to the target platform ===
 
=== Adding dependencies to the target platform ===

Revision as of 08:11, 6 May 2010

Introduction

The CDO project produces consumable builds for two separate streams. The integration stream build relates to the HEAD development and the maintenance stream build relates to the CVS branch (currently R2_0_maintenance) that always gets forked from HEAD after the yearly GA release. The builds are defined in terms of a Buckminster releng component and are executed by two Hudson CI build jobs.

This article is not meant to be a complete description of the various used concepts from Buckminster and Hudson. It's rather supposed to be an ongoing work to record the experiences with these builds and the actions taken to address particular issues.

The Releng Component

The CDO releng component is the org.eclipse.emf.cdo.releng project in your workspace if you followed CDO Source Installation. There are versions for both streams in CVS. The HEAD version looks roughly like this:

Releng-component.png

The remainder of this section lists some typical releng tasks that lead to modification of one or several of the files in the releng component. Here is an overview of how they relate to each other:

Releng-files.png

Adding dependencies to the target platform

Buckminster deduces the overall set of the needed dependencies

The Hudson Jobs