Skip to content
Snippets Groups Projects
Select Git revision
  • d5d8ebd10c4197fec45eba85150b54d56e7015bd
  • master default protected
  • all-src-revs
  • enhance-gitlab-backup
  • changelog-generator-all-projects
  • yt-xxx-ci-test-build-fails-1
  • yt-xxx-ci-test-build-fails
  • yt-65-troubleshoot-meta-freescale
  • yt-65-proxy-solution-for-repo-checkout
  • yt-93-improve-release-workflow-too-many-buttons-click-mock-test
  • troupbleshoot-qtkuktest-fail-due-privat-key
  • debug_credentials
  • generate-package-add-name
  • test_repo_verbose
  • build-documentation-in-dedicated-pipeline
  • seco-santvent-fsl
  • skip-deploy-if-target-not-set
  • add-pydoc-config
  • build-seco-image-after-fngsystem
  • store-build-variables
  • add-lava-testreposrting
21 results

gitlab-ci

  • Open with
  • Download source code
  • Your workspaces

      A workspace is a virtual sandbox environment for your code in GitLab.

      No agents available to create workspaces. Please consult Workspaces documentation for troubleshooting.

  • gitlab-ci Repository

    This repository contains GitLab CI scripts for Yocto infrastructure tasks, e.g. automatic integration of project changes into the manifest. It is meant to be included into all relevant Yocto repositories as a git submodule.

    The GitBot user

    Most scripts inside this repository need a personal GitLab access token of a user with access to all relevant repositories (manifest and all contained projects) in order to work correctly. We have created the @gitbot user for this task. The login credentials for it are stored in our KeePass safe. These should not be needed, though, as the user is member of the seco-ne group and thus already has access to all group projects. However, everyone can add the user as a member to every project he has access to, if needed.

    The personal access token of the @gitbot is provided via the CI environment variable GITBOT_TOKEN for all projects in the seco-ne group (set in the group's CI/CD settings under "Variables").

    Automatic manifest integration

    See this chapter for information on how the automatic integration process works:

    ▶️ Automatic manifest integration

    Deployment

    See this chapter for information on how to deploy changes in the gitlab-ci repository to all repositories that are using it.

    ▶️ gitlab-ci Deployment

    Manifest pipeline

    See this chapter for the pipeline runnning in the manifest repository to build the images.

    ▶️ manifest Pipeline