| Advantage | Description |
|---|---|
| Source control | Changes to source code and build scripts can be requested, developed, reviewed, approved, delivered, and tracked based on the requirements of your development project. Build scripts are living files, just like the source code. |
| Build automation | The Jazz™ Build Engine automatically
loads the workspace to build onto the build computer early in the
processing of a build request. You can create and use a dedicated
build workspace for each build definition. Do not point a build definition
directly to a stream or to a workspace that is meant for another purpose.
For example, do not point a build definition directory to the personal
workspace of a user or a team integration workspace. Note: The Jazz Build Engine is
a component of the Build System Toolkit;
it refers to the process that runs on a build computer and runs Ant
scripts.
|
| Static resource | Description |
|---|---|
| Oracle JDK | Use this JDK for running the Ant scripts and Android SDK tools that are run by the build scripts. Ensure that you install a JDK, not a JRE, because some Ant tasks require Java™ tools that are available only in the JDK. |
| Apache Ant | Use Apache Ant to run the Ant scripts. |
| JAR library files | The following JAR library files provide and
enable the Worklight Ant
tasks that are used in the build scripts:
Important: Ensure that the version of the
JAR library file that you use (worklight-ant.jar or worklight-ant-builder.jar)
matches the version on the target server.
Tip: An
alternative approach to preinstalling the JAR library files on each
build computer is to include them in your build workspace. This approach
allows your build definitions and engines to build with different
versions of Worklight.
This approach also supports the generation of reproducible builds.
The disadvantage of this approach is that the JAR library files can be large. The large file size might affect the performance of builds and build computers. If you share a build system and build computers across multiple teams, use this alternative approach to manage the JAR library files. |
| Optional. Dojo Toolkit | Install the Dojo Toolkit on each build computer
in the following situations:
|
| SDK | Description |
|---|---|
| Apple Xcode SDK | Install on OS X build computers that run builds to produce iOS IPA applications. For more information about installing the Apple Xcode SDK, see Getting Started with IBM Worklight Module 02.1 – Setting Up Your iOS Development Environment. |
| Android SDK | Install on build computers that run builds to produce Android APK applications. For more information about installing the Android SDK, see Getting Started with IBM Worklight Module 02.2 – Setting Up Your Android Development Environment. |