Differences between revisions 4 and 5
Revision 4 as of 2004-03-07 17:36:19
Size: 1511
Editor: 1Cust43
Comment:
Revision 5 as of 2004-03-07 17:41:03
Size: 1515
Editor: 1Cust43
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
 1. The pre-build steps are:
 a. Create directories for <mkdir
 *** Delete directories for <delete Note: Currently disabled for security.
 ** Build using script or ant (or maven). Classpath is determined/set.
 ** State is set/propogated based of exit code.
 ** The post-build steps are:
 *** Check all outputs (jars/licenses) exist, or set state to failed.
 *** Copy outputs to Jar repository
 *** 'List' certain files (maven log, junit reports, etc.)
Line 35: Line 26:
=== Pre-build steps ===
 * Create directories for <mkdir
 * Delete directories for <delete Note: Currently disabled for security.

=== Build steps ===
 * Build using script or ant (or maven). Classpath is determined/set.
 * State is set/propogated based of exit code.

=== Post-build steps ===
 * Check all outputs (jars/licenses) exist, or set state to failed.
 * Copy outputs to Jar repository
 * 'List' certain files (maven log, junit reports, etc.)

GumpInternals

Processing Step #1: Constructing Memory Structures

  • The GumpMetadata is loaded (via file/HTTP) and 'completed' into the GumpModel

  • The GumpModel is a tree of a workspace containing modules, which contain projects

  • Projects in the tree are linked (bi-directionally) via dependencies.
  • A GumpRun is build using a pattern match expression against project names, which contains the build sequence [of modules/projects].

Processing Step #2 : Performing the Work

Packages

  • ["Packages"] are determined (and their state set to 'complete' or 'failed').

Updating from Source Control

  • For updates, the build sequence of modules is traversed, any in a good state are cvs|svn updated. Any failures are propogated (see StatePropogation).

Build

  • The build sequence of projects is traversed, any in a good state have the following:

Pre-build steps

  • Create directories for <mkdir

  • Delete directories for <delete Note: Currently disabled for security.

Build steps

  • Build using script or ant (or maven). Classpath is determined/set.
  • State is set/propogated based of exit code.

Post-build steps

  • Check all outputs (jars/licenses) exist, or set state to failed.
  • Copy outputs to Jar repository
  • 'List' certain files (maven log, junit reports, etc.)

Processing Results

  • RSS and Atom feeds are generated be walking the tree.
  • A results.xml is generated, by walking the tree.

GumpInternals (last edited 2009-09-20 23:49:22 by localhost)