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 "EclipseLink/Build"
m (→Build Requirements) |
|||
Line 13: | Line 13: | ||
** Nightly should use same system, or at least not interfere at all with Eclipse/Dev builds | ** Nightly should use same system, or at least not interfere at all with Eclipse/Dev builds | ||
− | == Build Schedule == | + | == Build Automation == |
+ | EclipseLink utilizes automated build processes and methodologies for nearly all aspects of build processing. In some cases, like milestone and release publication, the build scripts need to be manually initiated to start the automated processes. In others, the processes are initated automatically - as is the case for the continuous and nightly integration builds. This section is dedicated to providing general information about these processes. | ||
+ | |||
+ | === Build Schedule === | ||
'''Nightly builds''' | '''Nightly builds''' |
Revision as of 11:27, 11 August 2010
Build Requirements
Past requirements used in designing the build
- Need reproducable Build automation quickly
- EclipseLink component builds need to be runnable on other non-eclipse IDEs (IntelliJ, JDev, etc)
- EclipseLink component builds need to be able to execute from either the hierarchical (SVN) tree, or a flat directory structure (all components at the same level
Moving Forward
- EclipseLink needs to shift from the old JEE to OSGi centric organization
- Builds should rely upon the manifest info for compile and runtime dependency info/versioning
- Any given component should build only when the component code changes
- Bundle version info should be updated per actual component build (split marketing and bundle versioning)
- 'Features' should dynamically generate (currently mostly hard-coded)
- Nightly should use same system, or at least not interfere at all with Eclipse/Dev builds
Build Automation
EclipseLink utilizes automated build processes and methodologies for nearly all aspects of build processing. In some cases, like milestone and release publication, the build scripts need to be manually initiated to start the automated processes. In others, the processes are initated automatically - as is the case for the continuous and nightly integration builds. This section is dedicated to providing general information about these processes.
Build Schedule
Nightly builds
- Trunk: 12:05a nightly
- 2.1.1: 1:35a nightly
- 2.0.3: 3:05a SuTThSa
- 1.2.1: 3:05a MWF
Continuous builds
- Trunk: On the hour (6a-8p)
- 2.1.1: 20 minutes after the hour (6a-8p)
- 2.0.3: 40 minutes after the hour (6a-8p)
All times are EDT.
Related Links
Links to other EclipseLink Build related pages:
EclipseLink/Building - http://wiki.eclipse.org/EclipseLink/Building
EclipseLink/Infrastructure - http://wiki.eclipse.org/EclipseLink/Infrastructure
EclipseLink/Build/Antlr - http://wiki.eclipse.org/EclipseLink/Build/Antlr
EclipseLink/Build/Roadmap - http://wiki.eclipse.org/EclipseLink/Build/Roadmap