<?xml version="1.0" encoding="UTF-8"?>

<!-- 

============================================================================ 

Name        : helium_data_model.xml 

Part of     : Helium 

Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies).

All rights reserved.

This component and the accompanying materials are made available

under the terms of the License "Eclipse Public License v1.0"

which accompanies this distribution, and is available

at the URL "http://www.eclipse.org/legal/epl-v10.html".

Initial Contributors:

Nokia Corporation - initial contribution.

Contributors:

Description:

============================================================================

-->

<!--

This describes the allowed values for some of the fields:

property:

- editStatus: [must, recommended, allowed, discouraged, never] 

  type: [string, boolean, integer]

-->

<heliumDataModel xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="..\tools\common\schema\helium_data_model.xsd">

    <property>

        <name>archive.max.number.of.threads</name>

        <editStatus>allowed</editStatus>

        <type>integer</type>

        <description>Set the maximum number of threads running for archiving (for a parallel job).</description>

    </property>

    <property>

        <name>ats.ctc.host</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>CTC host, provided by CATS used to create coverage measurement reports. MON.sym files are copied to this location, for example "10.0.0.1". If not given, code coverage reports are not created</description>

    </property>

    <property>

        <name>ats.testrun.name</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Modify the test-run name if you have understanding of test.xml file or leave it as it is. Deafault value is a string consist of build id, product name, major and minor versions</description>

    </property>

    <property>

        <name>ats.plan.name</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Modify the plan name if you have understanding of test.xml file or leave it as it is. Deafault value is "plan" </description>

    </property>

    <property>

        <name>ats.trace.enabled</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Should be "True" if tracing is needed during the tests running on ATS3. Deafault value is "False", the values are case-sensitive. </description>

    </property>

    <property>

        <name>ats.ctc.enabled</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Should be "True" if coverage measurement and dynamic analysis (CTC) tool support is to be used by ATS. Deafault value is "False", the values are case-sensitive. </description>

    </property>

    <property>

        <name>ats.email.list</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>The property is needed if you want to get an email from ATS server after the tests are executed. There can be one to many semicolon(s) ";" separated email addresses.</description>

    </property>

    <property>

        <name>ats.aste.email.list</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>The property is needed if you want to get an email from ATS server after the tests are executed. There can be one to many semicolon(s) ";" separated email addresses.</description>

    </property>

    <property>

        <name>ats.flashfiles.minlimit</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Limit of minimum number of flash files to execute ats-test target, otherwise ATSDrop.zip will not be generated. Default value is "2" files.</description>

    </property>

    <property>

        <name>ats.sisfiles.minlimit</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Limit of minimum number of sis files to execute matti-test target, otherwise MATTI-drop.zip will not be generated. Default value is "1" files.</description>

    </property>

    <property>

        <name>ats.target.platform</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Sets target platform for compiling test components. Default value is "armv5 urel".</description>

    </property>

    <property>

        <name>ats.test.timeout</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>To set test commands execution time limit on ATS3 server, in seconds. Default value is "60".</description>

    </property>

    <property>

        <name>ats.product.hwid</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Product HardWare ID (HWID) attached to ATS. By default the value of HWID is not set.</description>

    </property>

    <property>

        <name>ats.obey.pkgfiles.rule</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>If the property is set to "True", then the only test components which will have PKG files, will be included into the test.xml as a test-set. Which means, even if there's a test component (executable) but there's no PKG file, it should not be considered as a test component and hence not included into the test.xml as a separate test. By default the property value is False.</description>

    </property>

    <property>

        <name>tsrc.data.dir</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>The default value is "data" and refers to the 'data' directory under 'tsrc' directory.</description>

    </property>

    <property>

        <name>tsrc.path.list</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Contains list of the tsrc directories. Gets the list from system definition layer files. Assuming that the test components are defined already in te layers.sysdef.xml files to get compiled. 

        Not recommended, but the property value can be set if there are no system definition file(s), and tsrc directories paths to set manually.</description>

    </property>

    <property>

        <name>ats.flash.images</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>List of flash images (.fpsx files) to install on the phone. It is not recommended to set the value manually however, it is possible.</description>

    </property>

    <property>

        <name>ats.report.location</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Sets ATS reports store location. Default location is "${publish.dir}/${publish.subdir}"</description>

    </property>

    <property>

        <name>ats.drop.file</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Path for creation of the drop file during the build. Default is ATS3Drop.zip</description>

    </property>

    <property>

        <name>ats.aste.drop.file</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Path for creation of the drop file during the build. Default is ATS3AsteDrop.zip</description>

    </property>

    <property>

        <name>ats.product.name</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Name of the product to be tested. For example: "PRODUCT"</description>

    </property>

    <property>

        <name>ats.script.type</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>There are two types of ats script files to send drop to ATS server, "runx" and "import"; 

        only difference is that with "import" ATS doesn't have to have access rights to testdrop.zip file, 

        as it is sent to the system over http and import doesn't need network shares. 

        If that is not needed "import" should not be used. Default value is "runx" as "import" involves heavy processing on ATS server</description>

    </property>

    <property>

        <name>ats.drop.location</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Server location (UNC path) to save the ATS3Drop file, before sending to the ATS. For example: \\trwsem00\some_folder\. In case, ``ats.script.type`` is set to "import", ATS doesn't need to have access to ats.drop.location,  its value can be any local folder on build machine, for example c:\temp (no network share needed).</description>

    </property>

    <property>

        <name>ats.aste.testrun.name</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Modify the test-run name if you have understanding of test.xml file or leave it as it is. Deafault value is a string consist of build id, product name, major and minor versions</description>

    </property>

    <property>

        <name>ats.aste.plan.name</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Modify the plan name if you have understanding of test.xml file or leave it as it is. Deafault value is "plan" </description>

    </property>

    <property>

        <name>disable.analysis.tool</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Set this property to disable Analysis Tool. By default Analysis Tool will run with every build and send api metrics to diamonds but Analysis Tools takes time.</description>

    </property>

    <property>

        <name>drop.file.counter</name>

        <editStatus>never</editStatus>

        <type>integer</type>

        <description>Drop package file counter. Updates its value automatically when a new drop file is created for ATS.</description>

    </property>

    <property>

        <name>ido.build.filter</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Property is used to define ido build filters in the configuration file.</description>

    </property>

    <property>

        <name>ats.server</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>For example: "4fio00105" or "catstresrv001.cats.noklab.net:80". Default server port is "8080", but it is not allowed between intra and Noklab. Because of this we need to define server port as 80. The host can be different depending on site and/or product.</description>

    </property>

    <property>

        <name>ats.password</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Password for ATS. This password might be different from NOE or HTTP/UNIX password.</description>

    </property>

    <property>

        <name>ats.username</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Username for ATS server. This is NOT the NOE or HTTP/UNIX username.</description>

    </property>

    <property>

        <name>eunit.test.package</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>The EUnit package name to be unzipped on the environment, for executing EUnit tests."</description>

    </property>

    <property>

        <name>eunitexerunner.flags</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Flags for EUnit exerunner can be set by setting the value of this variable. The default flags are set to "/E S60AppEnv /R Off".</description>

    </property>

    <property>

        <name>cache.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Root directory where Helium can store files on a temporary basis for a user.</description>

    </property>

    <property>

        <name>log4j.cache.dir</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Log directory for log4j.</description>

    </property>

    <property>

        <name>build.cache.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Directory where Helium can store files on a temporary basis for a user per build.</description>

    </property>

    <property>

        <name>build.cache.log.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Directory where Helium can store log files on a temporary basis for a user per build.</description>

    </property>

    <property>

        <name>build.duplicates.log</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Default name of the build duplicates log file.</description>

    </property>

    <property>

        <name>build.version</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Version of the build.</description>

    </property>

    <property>

        <name>build.drive</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Substed drive where the build is performed. if not defined then helium should search next available build drive letter and subst autometically</description>

    </property>

    <property>

        <name>unsubst.after.build</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Unsubsted drive after build finished. If not defined then helium should left the drive as subst. Set the value as "yes" if you want to unsubst after build finished. </description>

    </property>

    <property>

        <name>build.id</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>A unique ID for the build.</description>

    </property>

    <property>

        <name>zip.wa.file</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>A unique name for the WA Sources ZIP file.</description>

    </property>

    <property>

        <name>binary.root</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Defines location of binaries created in build. Used in check-capability target while generating capability scan report.</description>

    </property>

    <property>

        <name>build.log</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Defines name of the log file.</description>

    </property>

    <property>

        <name>build.log.dir</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>This is where the build logs are stored.</description>

    </property>

    <property>

        <name>build.signal.status.dir</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>This is where the signal related files are stored.</description>

    </property>

    <property>

        <name>build.status.email.template</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>This is the email template path where it updates the build status based on metadata database contents. The default file could (email_status.html.ftl under tools\common\template\log)be used as the base and any additional info could be added</description>

    </property>

    <property>

        <name>build.logging.key.stages</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description> Defines which stages are considered as key stages and logged.</description>

    </property>

    <property>

        <name>build.logging.start.stage</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Defines at which point logging is started.</description>

    </property>

    <property>

        <name>build.name</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>A general label for this type of build. Currently if not defined, product.name will be used to set this property, but this will likely be removed in future.</description>

    </property>

    <property>

        <name>build.output.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>This is the directory where build output is placed.</description>

    </property>

    <property>

        <name>build.property.cache.file</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>A file where persistent properties for a build should be stored.</description>

    </property>

    <property>

        <name>build.sisfiles.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>This is the directory where sisfiles are placed.</description>

    </property>

    <property>

        <name>build.summary.file</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>This is the file where build summary is stored.</description>

    </property>

    <property>

        <name>build.system</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>This specifies which build system is used. Default for this is ebs You can use ec for Electric Cloud..</description>

    </property>

    <property>

        <name>build.system.ebs</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Defined if build.system is set to "ebs", which is the default.</description>

    </property>

    <property>

        <name>build.system.sbs</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Defined if ${build.system} is set to "sbs".</description>

    </property>

    <property>

        <name>build.temp.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>A directory for storing temporary build files.</description>

    </property>

    <property>

        <name>build.type</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>The general type of the build. This is used for checking the tools environment. Potential values include core, ido, product.</description>

    </property>

    <property>

        <name>build.errors.limit</name>

        <editStatus>allowed</editStatus>

        <type>number</type>

        <description>Maximum allowable errors in a build.</description>

    </property>

    <property>

        <name>canonical.sysdef.file</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>The path of the generated canonical System Definition file that contains all the input System Definition file content.</description>

    </property>

    <property>

        <name>ccm.base.dir</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Directory where CCM operations will be performed.</description>

    </property>

    <property>

        <name>ccm.home.dir</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Home directory of CCM operations.</description>

    </property>

    <property>

        <name>ccm.database</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Name of the CCM database to use. No default value.</description>

    </property>

    <property>

        <name>ccm.cache.xml</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Location of the cache.xml file which enables global synergy sessions.</description>

    </property>

    <property>

        <name>ccm.database.path</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Path of the CCM database. No default value</description>

    </property>

    <property>

        <name>ccm.enabled</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Defines that property if you want the ccm-get-input step to be run during the build area preparation.</description>

    </property>

    <property>

        <name>ccm.engine.host</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Engine host of CCM database. No default value.</description>

    </property>

    <property>

        <name>ccm.user.login</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Contains the user name for CCM by reading the information from .netrc file.</description>

    </property>

    <property>

        <name>ccm.user.password</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Contains the password for CCM user name by reading the information from .netrc file.</description>

    </property>

    <property>

        <name>ccmgetinput</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>To check which ccmgetinput helium will be use </description>

    </property>

    <property>

        <name>ccmtask.python.script.file</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>The path for the Python script to handle the ccm task bridge to the ccm.py module.</description>

    </property>

    <!-- CMAKER -->

    <property>

        <name>cmaker.component.dir</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Location of the cmaker component to install it.</description>

    </property>

    <property>

        <name>cmaker.config.dir</name>

        <editStatus>discouraged</editStatus>

        <type>string</type>

        <description>Directory where to execute cMaker.</description>

    </property>

    <property>

        <name>cmaker.log.label</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Custom label added to the cmaker logs.</description>

    </property>

    <property>

        <name>cmaker.pp.version</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Version of PP(NCP) configuration to be exported</description>

    </property>

    <property>

        <name>cmaker.s60.version</name>

        <editStatus>recommended</editStatus>

        <type>string</type>

        <description>Version of S60(require cmaker.pp.version to be set) configuration to be exported</description>

    </property>

    <property>

        <name>common.overlay.dir</name>

        <editStatus>must</editStatus>

        <type>string</type>

        <description>Location of the common overlay.</description>

    </property>

    <property>

        <name>current.env.config</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>Internal property used for environment setting in the beginning of the build.</description>

    </property>

    <property>

        <name>ctool.region.china</name>

        <editStatus>never</editStatus>

        <type>string</type>

        <description>.</description>

    </property>

    <property>

        <name>ctool.dir</name>

        <editStatus>allowed</editStatus>

        <type>string</type>

        <description>Location of the configuration tool.</description>