Skip to content
Snippets Groups Projects
Select Git revision
  • integrate/gitlab-ci/CI-report-image-diff/into/main
  • main default protected
  • integrate/gitlab-ci/kirkstone-spdx/into/main
  • integrate/gitlab-ci/test-gitbot-service-account/into/main
  • integrate/gitlab-ci/cleaos-552-build-cleaos-on-hamburgs-ci-servers-test/into/main
  • integrate/gitlab-ci/changelog-generator-all-projects/into/main
  • add-debug-page-with-input
  • dunfell protected
  • kirkstone protected
9 results
Blame History Permalink
  • GitBot's avatar
    Integrate gitlab-ci/yt-160-gitlab-ci-integration-often-fails-on-merge-yocto-step · 8a7f85a5
    GitBot authored 
    --

Commit: seco-ne/yocto/infrastructure/gitlab-ci@ff906931

YT-160: Workaround to prevent CI integration failure in 'merge-yocto' step

  The GitLab CI integration job frequently fails on the 'merge-yocto' step,
  specifically at the "git fetch" stage.
  The issue occurs because Git fails to fetch the .gitlab-ci submodule
  due to an incorrect reference, likely caused by the shallow clone
  (--depth=1) configuration, which limits the commit history.

  Extending the clone depth to --depth=2 helps prevent this error
  by providing a slightly deeper commit history,
  which resolves the reference issue.
    8a7f85a5
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
.gitlab-ci.yml 518 B 
---
# ---------------------------------------------------------------------------------------
# Include the default CI steps from the gitlab-ci repo
# ---------------------------------------------------------------------------------------
include:
  - project: '${CI_PROJECT_ROOT_NAMESPACE}/yocto/infrastructure/gitlab-ci'
    ref: ff906931bfb8018298518f539b73f4107abe7e7b
    file: 'manifest-integration.yml'

variables:
  GITLAB_CI_REVISION: ff906931bfb8018298518f539b73f4107abe7e7b
  BB_RECIPE_NAME: seco-show-demo