Skip to content
Snippets Groups Projects
Select Git revision
  • CI-report-image-diff
  • troubleshoot-report-image-diff
  • enhance-gitlab-backup
  • master default protected
  • 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
20 results
Compare History
Jonas Höppner's avatar
CI, release task: Use list created in yocto, don't rename files
Jonas Höppner authored 
Don't rename the release artifacts, just copy to a versioned folder.
The list of files to copy is taken from variables set in yocto
DISTRO_ARTIFACTS and DISTRO_IMAGES.
Images are linked, all other files are copied.

BCS 746-000273
c18d32a5
Name Last commit Last update
.gitignore
.gitlab-ci.yml
README.md
accept_merge_request.py
check_if_integration_branch_is_up_to_date.py
check_pipeline_status.py
common.py
get_manifest_projects.py
get_merge_requests.py
integrate_into_manifest.py
merge_into_manifest.py
package_release.py
pylintrc
retrigger_mr_pipeline_job.py
retrigger_mr_pipeline_jobs.py
README.md

gitlab-ci

GitLab CI scripts

This repository contains 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.

Providing GITBOT_TOKEN

The scripts 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 @guf-gitbot user for this task. Norman and Tim know the login credentials for it. These should not be needed, though, as the user is member of the Garz & Fricke 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 @guf-gitbot user has to be provided on each repository via the CI environment variable GITBOT_TOKEN (set under project's settings -> CI/CD -> Variables). Its value can be read on projects which already have this variable defined.