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.
EGF Build Portfolio
Contents
Portfolio Name
Build Portfolio
Objective and scope
The objective of the Build Portfolio is to edit a build chain and next generate all the associated files for a release engineering target platform in order to manage and control a build chain.
The purpose is not to have an exhaustive, and then complex, build description. The build description must be simple with the possibility to describe large build chains.
The portfolio targets first Hudson and Buckminster.
Rationale
MDA principle
In OMG's MDA terms, the edited model represents the PIM and the build chain against a build target platform represents the PSM.
The PIM-to-PSM transformation is realized by a generation ensured by EGF. During this generation 1) the build model is transformed to be optimized, 2) the transformed model is checked, 3) files for the target platform are generated.
Concepts
| Name | Description |
 Job
|
List of steps |
 SCM Configuration
|
Type of SCM locations |
 SCM Location
|
SCM locations (e.g., svn url) |
 Build Step
|
Materializes and builds a workspace |
  Dependencies
|
Sources and dependencies locations |
  Components
|
Features and plugins to find and build |
 Junit Step |
Launches a Junit launch configuration |
 Publish Step |
Generates P2 site and dropins |
 EGF Step |
Launches an EGF activity |
 Aggregation Step |
Aggregates several P2 sites and dropins |
 Ant Step |
Launches a custom ant target |
 Javadoc Step |
Generated Javadoc from sources |
Process
[TBD]
Example
Download the EGF examples and import the org.eclipse.egf.portfolio.eclipse.build.examples plugin.
References
A video is available here