Show TOC

Downloading DC ArchivesLocate this document in the navigation structure

Context

Variants

From the sources of a compartment, the build service can create several variants that:

  • differ because of the selection of special parameters for the used compilers or generators an example is the generation of an "optimized" and a "debugging" variant.

  • are designed for different operating systems or runtime environments.

  • consider country-specific or language-specific peculiarities.

Variants have names that must be unique within a configuration. For every compartment, at least one variant must be defined.

The development configuration contains a list of variants for every compartment. Not all compartments must offer the same variants. If variants are defined for a compartment, the compartment provides specific libraries and deployable archives for every component and every variant (build variants).

Example

A compartment determines that a component SC X creates a "debugging" and an "optimized" variant. The variants differ only in the fact that the compilers and generators are called with different options. The variants carry the identifiers "dbg" und "opt". The component is designed to support two different operating systems so that all in all four variants must be built: "linux/dbg","linux/opt","win/dbg" und "win/opt". Finally, the component is translated into different languages so that the number of variants must be multiplied with the number of supported languages: "de/linux/dbg", "en/linux/dbg", "de/linux/opt" and so on.

The identifiers of variants can be defined separately for every compartment. However, during the import of archives from other configurations, a compartment rejects those variants for which no own variant exists in the target. This is done using a simple comparison of the variant identifiers.

Note

In a large development landscape, it is recommendable to define uniform identifiers for variants and to use them exclusively.

Required Variants

When activating changes in the build service, all variants defined for a compartment of a component are built. However, it may not be necessary for a successful activation that all variants must be built without errors. An "optimized" variant of a component can, for example, be dispensable if a "debugging" variant exists. Therefore, you can determine for every variant whether it is required for a successful activation.

Caution

If there are errors in the build of required variants, the activation of changes is rejected.

Procedure


  1. Start the CBS Web UI.

  2. Select the Development Component Details View .

  3. Select the Download Archives tab strip.

  4. Select the build variant you need as a download for the archives.

  5. Select the link for the required archive type.