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 "EclipseLink/Build"

(Automated Build Schedule)
Line 12: Line 12:
 
** 'Features' should dynamically generate (currently mostly hard-coded)
 
** 'Features' should dynamically generate (currently mostly hard-coded)
 
** 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
 +
  
 
== Automated Build Schedule ==
 
== Automated Build Schedule ==
Line 26: Line 27:
  
 
: <u>''1.2.1'':</u>  3:05a MWF
 
: <u>''1.2.1'':</u>  3:05a MWF
 +
  
 
'''Continuous builds'''
 
'''Continuous builds'''
Line 36: Line 38:
  
 
All times are EDT. The crontab entries can be directly viewed in cron.txt which is stored in the /buildsystem directory of the trunk branch in our svn repository.
 
All times are EDT. The crontab entries can be directly viewed in cron.txt which is stored in the /buildsystem directory of the trunk branch in our svn repository.
 +
  
 
== Related Links ==
 
== Related Links ==

Revision as of 12:28, 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


Automated Build Schedule

EclipseLink utilizes automated build processes and methodologies for nearly all aspects of build processing. In some cases, like milestone and release publication, the automated processes are manually initiated. While others, the continuous and nightly integration builds, are initated automatically via crontab. For a more detailed discussion of the automated processes see the EclipseLink/Infrastructure page.


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 daily)
2.1.1: 20 minutes after the hour (6a-8p daily)
2.0.3: 40 minutes after the hour (6a-8p daily)

All times are EDT. The crontab entries can be directly viewed in cron.txt which is stored in the /buildsystem directory of the trunk branch in our svn repository.


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

Back to the top