Factory Definition

Each Factory can be customized to control how CI handles it. This is managed in the “Factory Definition” which is located in a factory’s ci-scripts.git repository in the factory-config.yml file.

notify:
email:
users: <email_1>,<email_2>,<...>
Required: Comma separated list of addresses to email after each CI build.
failures_only: <true|false>

Optional: If set to true users will only be notified of CI failures.

Default: false

lmp:
params:
IMAGE: <lmp_image_type>
Required: Define the LmP image type you want to produce.
EXAMPLE_VARIABLE_1: <value>
Optional: Define an arbitrary environment variable to be passed into the LmP build. You can define as many as you want.
machines:
- <machine_1>
- <machine_2>
Required: Specify the list of Supported LmP Machines to build for by their MACHINE name. A Factory’s subscription is generally only good for a single machine.
ref_options:
refs/heads/<branch>:

Optional: Override options when specific git references are updated

Example:

# In the below example, when the branch named "devel" is built by our
# CI system, it will have its option values for "machine" and
# "params" overriden by what is specified after "refs/heads/devel:".
# In the "devel" build, IMAGE will now equal "lmp-mini" rather than
# "lmp-factory-image" as initially defined.

lmp:
  params:
    IMAGE: lmp-factory-image
  machines:
    - imx8mmevk
  ref_options:
    refs/heads/devel:
      machines:
        - raspberrypi3-64
      params:
        IMAGE: lmp-mini
tagging:
refs/heads/<branch>:
-tag: <tag>
Optional: Control how OTA_LITE tags are handled. See Advanced Tagging for more details.
mfg_tools:
- machine: <machine>
Optional: Do an OE build to produce manufacturing tooling for a given MACHINE. This is used to facilitate the manufacturing process and to ensure secure boot on imx devices.
containers:
platforms:
- arm
- arm64
- amd64

Optional: Specify a list of architectures to build containers for. Containers are only built for the specified list.

Default: amd64

tagging:
refs/heads/<branch>:
-tag: <tag>
Optional: Control how OTA_LITE tags are handled. See Advanced Tagging for more details.