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 "Athena Common Build"
(→Ongoing Development) |
(→System) |
||
Line 18: | Line 18: | ||
* automatic build cleanup / expiry | * automatic build cleanup / expiry | ||
* configuration to be done in Portal | * configuration to be done in Portal | ||
− | * | + | * solution for scheduling builds (eg. crontab-based) |
− | * | + | * continuous builds (build queuing, repo watching) |
* support for java-only, simple project builds (not products) | * support for java-only, simple project builds (not products) | ||
* support for building on Linux only (no Win or Mac shared libraries) | * support for building on Linux only (no Win or Mac shared libraries) | ||
− | * builds must be reproduceable ( | + | * builds must be reproduceable (tagging) |
* one build per project or component | * one build per project or component | ||
* mechanism for producing signed, packed, and digested update sites w/ p2 metadata | * mechanism for producing signed, packed, and digested update sites w/ p2 metadata | ||
+ | * support for Eclipse SCM systems (cvs + svn) | ||
== Cross-Project Integration == | == Cross-Project Integration == |
Revision as of 04:17, 2 February 2009
This article is a stub. You can help Eclipsepedia by expanding it.
Order of listed items below should not be taken as priority sequence. For prioritization, see Project Plan (Draft), or the following bugzilla queries:
Contents
Requirements
End User
- properly-defined plugins and features (see JET Transforms/Wizards for creating project meta data)
- a .releng project (see JET Transforms/Wizards for creating project meta data)
System
- UI for running, exploring, validating & promoting builds; UI for killing / purging invalid builds
- automatic build cleanup / expiry
- configuration to be done in Portal
- solution for scheduling builds (eg. crontab-based)
- continuous builds (build queuing, repo watching)
- support for java-only, simple project builds (not products)
- support for building on Linux only (no Win or Mac shared libraries)
- builds must be reproduceable (tagging)
- one build per project or component
- mechanism for producing signed, packed, and digested update sites w/ p2 metadata
- support for Eclipse SCM systems (cvs + svn)
Cross-Project Integration
- mechanism for optionally contributing update site feature(s) to a coordinated release site, a la Ganymede
Enhancements
- support feeding dependencies to build from update site instead of from zips
- support getting latest dependencies from RSS feeds
- support building & testing against multiple versions of target platform
- provide source builds to facilitate the build-from-source scenario (eg., Linux distros)
- automatic cleanup of downloaded/cached dependencies
- support Buckminster
- support SVN
- support Maven-based dependencies
- convert bash scripts that “do work” to Ant scripts w/ custom tasks; submitting these back to PDE build or releng.basebuilder for reuse
- convert bash scripts that “do calculations” to PHP-based web apis, so they can be called by web, shell, ant, or java
Sources
- Metagen Wizards for creating plugin, feature, and .releng projects (GSoC 2008 project, incubating)
- cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/technology -Q co -d org.eclipse.metagen org.eclipse.soc/athena
- Dash Common Build (beta, in progress, v4, 2009?)
- cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/technology -Q co -d org.eclipse.dash.commonbuilder org.eclipse.dash/athena/org.eclipse.dash.commonbuilder
- Modeling Common Build (stable release, v3, 2008)
- cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/modeling -Q co -d org.eclipse.modeling.common.releng releng-common
- EMFT Common Build (stable release, v2, 2007)
- deprecated by Modeling Common Build
- EMF Build (stable release, v1, 2006)
- cvs -d :pserver:anonymous@dev.eclipse.org:/cvsroot/modeling -Q co -d org.eclipse.emf.releng org.eclipse.emf/org.eclipse.emf.releng
Contributing
We're always looking for people to contribute. You can drop us a line at dash-dev@eclipse.org.
You can also subscribe to the Dash Commonbuilder Bugzilla inbox, find an open bug to work on (we love patches!), or open a new bug.