Skip to content
Snippets Groups Projects
Select Git revision
  • integrate/gitlab-ci/extend-image-diff-job-to-manifest-mrs/into/kirkstone
  • jonas/seco-sharedconf-yocto-install
  • integrate/gitlab-ci/CI-report-image-diff/into/kirkstone
  • kirkstone default protected
  • dunfell protected
  • integrate/gitlab-ci/kirkstone-spdx/into/kirkstone
  • integrate/gitlab-ci/test-gitbot-service-account/into/kirkstone
  • integrate/gitlab-ci/test-gitbot-service-account/into/dunfell
  • integrate/gitlab-ci/cleaos-552-build-cleaos-on-hamburgs-ci-servers-test/into/kirkstone
  • kirkstone-u-boot-env-unification
  • uuu-install-wic-update
  • kirkstone-update-uuu
  • integrate/gitlab-ci/changelog-generator-all-projects/into/kirkstone
  • kirkstone_tr8mm-ipant7
  • ci-test
  • tr8mp-v1r5-overlay
  • move_libubootenv
  • kirkstone-seco-mx6-fngboot-uboot-boot
  • debug_fngsystem_wic_nxp
  • add-mx93
  • rocko/10.2
  • rocko/8.3
  • rocko/10.1
  • 7.3
  • rocko/8.2
  • rocko/8.1
  • rocko/9.1
  • 4.2
  • 7.2
  • rocko/7.2
  • rocko/10.0
  • rocko/9.0
  • fngsystem/16.00
  • rocko/8.0
  • fngsystem/0
  • 7.1
  • rocko/7.1
  • 7.0
  • rocko/7.0
  • 6.0
40 results
Compare History
gitbot's avatar
Integrate gitlab-ci/separate-images-in-multiple-pipelines and 1 more
GitBot authored 
--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@9406ad75

Yocto build: separate images in multiple pipelines

Instead of building the Yocto image, the Yocto SDK and the FNGSystem
image in one single pipeline, separate them into three independent
pipelines that are triggered in parallel.

This makes the concept more modular: we have a single general pipeline
now which is configurable from outside via variables. Hence we can have
a custom number of pipelines along with custom build targets in each
project without having to make code changes in the gitlab-ci project.

The default Yocto manifest pipeline configures three build pipelines:

- yocto-build-jobs
- sdk-build-jobs
- fngsystem-build-jobs

In a project including the Yocto manifest pipeline, we can disable
certain build pipelines using job rules, e.g. disabling the SDK build:

sdk-build-jobs:
  rules:
    - when: never

Furthermore we can add more pipelines by simply adding jobs extending
the '.build-jobs' class in the project's .gitlab-ci.yml:

yocto-custom-build-jobs:
  extends:
    - .build-jobs
  variables:
    BITBAKE_TASK: build
    CI_PARAM_IMAGE: custom-image
    CI_PARAM_DISTRO: custom-distro
    PACKAGE_TYPE: image

--

Commit: seco-ne/yocto/infrastructure/gitlab-ci@447804d2

.gitlab-ci: increase analyze timeout
50f08393
Name Last commit Last update
classes
conf
dynamic-layers/freescale-layer/recipes-bsp
recipes-bsp
recipes-connectivity
recipes-kernel
recipes-seconorth
.gitlab-ci @ 9406ad75
.gitignore
.gitlab-ci.yml
.gitmodules
LICENSE.txt
README.md
README.md

meta-seconorth-machine

See README.md in the manifest project for project information.

This layer is intended to hold all recipes needed to build the Board Support Package (BSP) for SECO Northern Europe (by Garz & Fricke) boards.

It does not provide a buildable image. Instead the necessary the Yocto MACHINE abstraction is provided that can be use dto build a custom distribution.

However, the primary use-case for this layer is the combination with the meta-seconorth-distro layer to create a SECO Northern Europe standard image build environment. See the manifest for details.

License

This layer is licensed under the Apache License 2.0. See also LICENSE.txt inside the root directory. Recipes with deviating licenses have LICENSE.txt inside the recipe directories.