Build
-
Upload
bharat-malge -
Category
Software
-
view
123 -
download
0
Transcript of Build
Building with Rational Team Concert Build
Managing Builds in Rational Team Concert
Build component of the RTC provides support for the automation, monitoring, and awareness of builds for teams
Build system toolkit is basically includes build engine and ant build toolkitThe following are the build items which are stored in the Jazz repository and support the build process:
Build definition: Defines a build, such as a weekly project-wide integration build. Build engine: Represents a build system that runs on a dedicated server. Build request: Represents a request to run a build. Build result: Represents the output from a build.
And this build related items will belongs to only respective project area.
The Jazz build engine does not include a JDK, so by default it will use the system JDK or JRE.
Software build is the process of gathering the source code and other artifacts to churn them into executable software. Modern builds also provide traceability, association between artifacts and work items, reproducibility, IDE integration, and build comparison. With the increasing complexity of the software, builds too are becoming complex to manage. In this chapter, we will:
See an overview of the build engine, build a toolkit, learn how to define the build, and track progress from Eclipse and the Web UI
Work for Sprint 2 completion of the BookManager Project and deliver Release 1.0 to the main development line
Define builds, set up the build engine, and track the BookManager Project's builds from a developer and build user's perspectives
Prerequisites :
Assumming:
The Rational Team Concert 6.0 server is already set up, and you have access to theserver through Rational Team Concert Eclipse client.
The required source code for build is present in the Rational Team Concert project areasource control
The Build System Toolkit has been installed by using the IBM Installation Manager.
working with the repository workspace
Create a new repository workspace
Select components to add to the new repository workspace
Load all of the projects within the components
Never use Program Files as install location. It tends to create issues. Avoid ID's with spaces. I would use for example engine.ProjectX.
Build Using SCM.