Build Workshop 3: Build Hard With A Purpose/How Build Works

How CBI Builds work

Input

Required

1. Project ID (same as portal ex. tools.gef, technology.linuxtools) (-projectid)
2. Version to use (-version)
3. CVS Root for project's releng plugin (we will add SVN support soon) <-- could perhaps come from portal in future (-projRelengRoot)
4. CVS Path for project's releng plugin (we will add SVN support soon) <-- could perhaps come from portal in future (-projRelengPath)
5. URLs of dependencies (ex. http://download.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/eclipse-SDK-3.4-linux-gtk.tar.gz) (we will automate this more in the future) (-URL)

Optional

1. CVS branch of org.eclipse.releng.basebuilder (-basebuilderBranch)
2. JAVA_HOME (-javaHome)
3. Path to a local checkout of the source (avoids checking out during build) (-localSourceCheckoutDir)
4. Nick should probably fill in the rest with all of the options he has

Output

1. Master zip
2. SDK zip

Process

Entry point: start.sh

<!-- my comment -->
<xmlroot>
  <myelement myattribute="Hello">World</myelement>
</xmlroot >