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"

(Build Automation)
(Automated Build Schedule)
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
== Build Requirements ==
 
== Build Requirements ==
'''Past requirements used in designing the build'''
+
This section has been [http://wiki.eclipse.org/EclipseLink/Build/Requirements moved].
* Need reproducable Build automation quickly
+
* EclipseLink component builds need to be runnable on other [[EclipseLink/Examples/JPA#Integrating_EclipseLink_JPA_with_an_IDE|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 ==
 
== 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 in others, the continuous and nightly integration builds are initated automatically via crontab. For a more detailed discussion of the automated processes see the "Infrastructure" page.
+
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 initiated automatically via Hudson (https://hudson.eclipse.org/hudson/view/EclipseLink/). For a more detailed discussion of the automated processes see the [[EclipseLink/Infrastructure]] page.
  
'''Nightly builds'''
 
  
: <u>'Trunk'':</u> 12:05a nightly
+
'''Nightly build schedule by branch'''
  
: <u>''2.1.1'':</u> 1:35a nightly
+
: <u>'Master'':</u> 12:05a nightly
  
: <u>''2.0.3'':</u>  3:05a SuTThSa
+
: <u>''2.4'':</u>  1:35a nightly
  
: <u>''1.2.1'':</u>  3:05a MWF
+
: <u>''2.3'':</u>  3:05a nightly
  
'''Continuous builds'''
 
  
: <u>''Trunk'':</u> On the hour (6a-8p daily)
+
'''Continuous build schedule'''
  
: <u>''2.1.1'':</u> 20 minutes after the hour (6a-8p daily)
+
: <u>''Master'':</u> On the hour (6a-8p daily)
  
: <u>''2.0.3'':</u> 40 minutes after the hour (6a-8p daily)
+
: <u>''2.4'':</u> 20 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.
+
: <u>''2.3'':</u> 40 minutes after the hour (6a-8p daily)
 +
 
 +
 
 +
All times are EDT.
  
 
== Related Links ==
 
== Related Links ==
Line 41: Line 30:
  
 
[[EclipseLink/Building]] - http://wiki.eclipse.org/EclipseLink/Building
 
[[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/Antlr]] - http://wiki.eclipse.org/EclipseLink/Build/Antlr
 +
 +
[[EclipseLink/Build/Infrastructure]] - http://wiki.eclipse.org/EclipseLink/Build/Infrastructure
 +
 +
[[EclipseLink/Build/NextGen]] - http://wiki.eclipse.org/EclipseLink/Build/NextGen
 +
 +
[[EclipseLink/Build/Requirements]] - http://wiki.eclipse.org/EclipseLink/Build/Requirements
  
 
[[EclipseLink/Build/Roadmap]] - http://wiki.eclipse.org/EclipseLink/Build/Roadmap
 
[[EclipseLink/Build/Roadmap]] - http://wiki.eclipse.org/EclipseLink/Build/Roadmap
 +
 +
[[EclipseLink/Build/Tycho]] - http://wiki.eclipse.org/EclipseLink/Build/Tycho
 +
 +
[[EclipseLink/Build/Git]] - http://wiki.eclipse.org/EclipseLink/Build/Git
 +
 +
[[Category:EclipseLink|Build]]

Revision as of 14:57, 11 December 2012

Build Requirements

This section has been moved.

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 initiated automatically via Hudson (https://hudson.eclipse.org/hudson/view/EclipseLink/). For a more detailed discussion of the automated processes see the EclipseLink/Infrastructure page.


Nightly build schedule by branch

'Master: 12:05a nightly
2.4: 1:35a nightly
2.3: 3:05a nightly


Continuous build schedule

Master: On the hour (6a-8p daily)
2.4: 20 minutes after the hour (6a-8p daily)
2.3: 40 minutes after the hour (6a-8p daily)


All times are EDT.

Related Links

Links to other EclipseLink Build related pages:

EclipseLink/Building - http://wiki.eclipse.org/EclipseLink/Building

EclipseLink/Build/Antlr - http://wiki.eclipse.org/EclipseLink/Build/Antlr

EclipseLink/Build/Infrastructure - http://wiki.eclipse.org/EclipseLink/Build/Infrastructure

EclipseLink/Build/NextGen - http://wiki.eclipse.org/EclipseLink/Build/NextGen

EclipseLink/Build/Requirements - http://wiki.eclipse.org/EclipseLink/Build/Requirements

EclipseLink/Build/Roadmap - http://wiki.eclipse.org/EclipseLink/Build/Roadmap

EclipseLink/Build/Tycho - http://wiki.eclipse.org/EclipseLink/Build/Tycho

EclipseLink/Build/Git - http://wiki.eclipse.org/EclipseLink/Build/Git

Back to the top