General Configuration Items

The following section at the top of the file describes general information about the build configuration.

XML Example 1

XML Example 2

Description

<BuildConfigurations>

...

</BuildConfigurations>

<BuildConfigurations>

...

</BuildConfigurations>

Opening and closing tags for entire XML document.

All of the other tags in the entire document are contained between these two tags.

<BuildConfiguration Id="19">

...

</BuildConfiguration>

<BuildConfiguration Id="18">

...

</BuildConfiguration>

Opening and closing tags for entire build configuration.  

A single XML document may contain more than one individual build configuration with each one being contained between these two tags.

<BuildProject Id="4203131">

<project>

![CDATA[QLARIUS:UW_JAVA_2.0]]

</project>

<description>

![CDATA[Underwriter Desktop Java development project]]

</description>

</BuildProject>

<BuildProject Id="4203131">

<project>

![CDATA[QLARIUS:UW_JAVA_2.0]]

</project>

<description>

![CDATA[Underwriter Desktop Java development project]]

</description>

</BuildProject>

Parent project information. This section consists of:

  • project ID

  • project name

  • description.

<name>

![CDATA[JAVA_ANT]]

</name>

<name>

![CDATA[JAVA_JAVAC]]

</name>

Build configuration name.

<description>

![CDATA[Java sample using ant]]

</description>

<description>

![CDATA[Java sample using javac]]

</description>

Build configuration description.

<ProjectRelPath>

ABC

</ProjectRelPath>

 

Build configuration path relative to the Dimensions project it is assigned to.

This field allows the user to set a build configuration to a particular directory in the overall Dimensions project instead of being anchored on the root of the project.

<Platform Id="1">

<name>

![CDATA[Win32]]

</name>

</Platform>

<Platform Id="1">

<name>

![CDATA[Win32]]

</name>

</Platform>

Platform id and name.  

Valid values for this field are:

ID: 1  Name: Win32

ID: 2  Name: AIX

ID: 3  Name: HPUX

ID: 4  Name: Linux

ID: 5  Name: Solaris

ID: 6  Name: USS

ID: 7  Name: SCO

ID: 8  Name: MVS.  

<LaunchTimeout>

0

</LaunchTimeout>

<LaunchTimeout>

0   

</LaunchTimeout>

Launch Timeout.

When launching a build, this tag defines how many seconds the Build server waits before deciding the launch has failed if no communication is received from the remote build node. This value overrides the default value defined in web.xml.

<ExecutionTimeout>

0

</ExecutionTimeout>

<ExecutionTimeout>

0

</ExecutionTimeout>

Execution Timeout.

When executing a build, this tag defines how many seconds the Build sever waits before canceling a build job that has not communicated any status. This value overrides the default value defined in web.xml.

<ConfigurationType Id="1">

<name>

![CDATA[Default]]

</name>

<code>

![CDATA[DEFAULT]]

</code>

</ConfigurationType>

<ConfigurationType Id="1">

<name>

![CDATA[Default]]

</name>

<code>

![CDATA[DEFAULT]]

</code>

</ConfigurationType>

Configuration type. Is defined in Settings: Build Configuration Types and can be optionally assigned to a configuration.

<Options>

...

</Options>

 

Option to be used for this transition.  

This is defined by id (unique to database), option name, and option values. If the option values are related to a build tool, the relationship is also defined here.

<OptionGroupIds>

#

</OptionGroupIds>

 

Option Group id(s) (unique to database) tied to this transition.

<preScript Id=”285”>

<type>1</type>

<scriptName>

pre-script.bat

</scriptName>

</preScript>

 

Configuration pre-script: a script to be executed before all build processing has been started.

<mainScript Id=”286”>

<type>3</type>

<scriptContent>

ant –f build.xml

</scriptContent>

</mainScript>

 

Configuration main-script: a script to be executed on a target if no other script has been defined.

<postScript Id=”287”>

<type>2</type>

<ControlledAsset>

<binding>

I{ QLARIUS:UW_JAVA_2.0}templates/post-script.bat

</binding>

</ControlledAsset>

</postScript>

 

Configuration post-script: a script to be executed after all build processing is complete.

<cleanScript Id=”288”>

<type>1</type>

<scriptName>

clean-script.bat

</scriptName>

</cleanScript>

 

Configuration clean-script: a script to be optionally executed before the pre-script.

 (Sheet  of )