Structure of Pipeline folder

Binaries

The Biniaries folder should contain the following files and define necessary information:

• DLL used by the bootstrapping application.

• Manifests

  • Install_manifest_*

    • List of files that are within this component

    • Files within this must be distinct. (Each file must belong to one component.)

• Buildproduct.yml

  • Is passed to the pipelinerunner during build

  • Contains ALL available stages / steps. Etc.

  • Selection of stages to run is defined within the Build.ps1

• Config

  • Automation
    • Bundle stages: These files define the stages to be run for each bundle. You can produce up to three different bundles (by setting build = true). The name must correspond to the yml files in the "bundles" folder, starting with the prefix BA*, e.g.: BASetup.yml for the Setup bundle. To remove components, comment them out in the BA file.
    • Perparation stages: This controls the stage in which the OEM customizations are done.
    • Package stages: The file defines the build process for the packages.
  • Bundles This folder contains all files defining the components included in the specified bundles.
    • Bundle Config: This file defines all the dynamically added files, such as banners and localizations, eula. This is the maximal possible package.
  • Localization: This folder contains the definition of localized translations for the bootstrapping application, Bundlefeatures and msi packages within the installation bootstrapper
  • MsiPackages: This folder contains the definition files with the msi package build information.
  • ProductConfiguration: The files define the product information. Their content defines i.a. that, if multiple bundles are built, they can't be installed on the same machine.