Jump to: navigation, search

Difference between revisions of "Build Workshop 3: Build Hard With A Purpose/Inputs and Outputs"

(New page: Here.)
 
m
Line 1: Line 1:
Here.
+
Discussion regarding new form of the CBI as morphed from the Modeling Common Build.
 +
 
 +
Intent is simplest input, standard output, with options to produce more/different outputs FROM that output.
 +
 
 +
===Inputs===
 +
 
 +
* current specification (Modeling Common Build)
 +
:* .releng project
 +
::* defines feature(s) to build -- generally all-in-one/SDK feature + tests feature
 +
::* contains map files(s) to define where to get sources
 +
::* additional instructions (packaging / runtime 3rd party libs / ... )
 +
:* website meta / crontab details
 +
::* branch/version/JDKpath/basebuildertag/testsRunTrueFalse/dependencies (zips or orbit map)
 +
 
 +
* desired specification: one master properties file
 +
:* defines input zips (dependencies)
 +
:* defines 3rd party libs (incl. Orbit)
 +
:* hook to additional build.xml scripts for post-build repackaging (Master -> SDK -> Runtime, Examples, ...)
 +
 
 +
===Outputs===
 +
 
 +
* Current:
 +
 
 +
:*.releng/buildAll.xml defines build, test, and packaging for Master, SDK, Runtimes, Examples, Tests zips, including tweaking input/output for 3rd party libs (GPL stuff needed to build but which can't be distributed)
 +
 
 +
* Desired:
 +
 
 +
: one zip out (p2 repo format - signed/packed master zip)
 +
features/*.jar
 +
features/*.jar.pack.gz
 +
plugins/*.jar
 +
plugins/*.jar.pack.gz
 +
binaries/ (other artifacts, eg., from Platform or CDT)
 +
artifacts.jar
 +
content.jar
 +
 +
: hooks for producing other zips & unpacked p2-enabled update site/repo
 +
: ...
 +
 
 +
===Potential PDE changes===
 +
* specifying more than one input zip (?)

Revision as of 14:10, 22 October 2008

Discussion regarding new form of the CBI as morphed from the Modeling Common Build.

Intent is simplest input, standard output, with options to produce more/different outputs FROM that output.

Inputs

  • current specification (Modeling Common Build)
  • .releng project
  • defines feature(s) to build -- generally all-in-one/SDK feature + tests feature
  • contains map files(s) to define where to get sources
  • additional instructions (packaging / runtime 3rd party libs / ... )
  • website meta / crontab details
  • branch/version/JDKpath/basebuildertag/testsRunTrueFalse/dependencies (zips or orbit map)
  • desired specification: one master properties file
  • defines input zips (dependencies)
  • defines 3rd party libs (incl. Orbit)
  • hook to additional build.xml scripts for post-build repackaging (Master -> SDK -> Runtime, Examples, ...)

Outputs

  • Current:
  • .releng/buildAll.xml defines build, test, and packaging for Master, SDK, Runtimes, Examples, Tests zips, including tweaking input/output for 3rd party libs (GPL stuff needed to build but which can't be distributed)
  • Desired:
one zip out (p2 repo format - signed/packed master zip)

features/*.jar features/*.jar.pack.gz plugins/*.jar plugins/*.jar.pack.gz binaries/ (other artifacts, eg., from Platform or CDT) artifacts.jar content.jar

hooks for producing other zips & unpacked p2-enabled update site/repo
...

Potential PDE changes

  • specifying more than one input zip (?)