Skip to content
Snippets Groups Projects
  1. Feb 28, 2025
  2. Feb 11, 2025
  3. Jan 08, 2025
  4. Nov 18, 2024
  5. Nov 11, 2024
    • GitBot's avatar
      Integrate gitlab-ci/yt-260-restrict-edit-rights-on-confluence-release-page · 1bec0fe4
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@081272c1
      
      YT-260: Inherit restrictions from the parent Confluence page
      
        In each release, a Confluence page is created with expected restrictions
        specifying who can edit or update the page.
        Confluence automatically inherits "read" restrictions from the parent page,
        but "edit/update" restrictions are not inherited by design in Confluence.
        This ensures that restrictions are manually inherited from the parent page.
      
        Since the Confluence Python API module lacks functionality for
        setting restrictions, direct HTTP requests are used with the
        `requests` library instead of the Confluence module.
      1bec0fe4
  6. Oct 14, 2024
  7. Oct 10, 2024
  8. Oct 01, 2024
  9. Sep 30, 2024
    • GitBot's avatar
      Integrate gitlab-ci/yt-160-gitlab-ci-integration-often-fails-on-merge-yocto-step · 16ac773c
      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.
      16ac773c
  10. Sep 27, 2024
  11. Sep 20, 2024
    • GitBot's avatar
      Integrate gitlab-ci/changelog-generator-all-projects-YT-256 and 3 more · d4da2a81
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@f0ed0f4f
      
      CI: Changelog: Add new variable 'CHANGELOG_PROJECTS_SKIP', remove project list
      
      The listed projects for the changelog are now supposed to be found
      automatically. No need to list them anymore.
      The 'SKIP' variable is mostly ment for custom projects, to filter out
      unneeded projects from the changelog.
      
      YT-256
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@434d542a
      
      get_integration_source: Print warning to stderr instead of stdout
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@5cc674f7
      
      Changelog: Include all related projects into the changelog
      
      In build-pipeline.yml, enable the new parameter by default.
      
      YT-256
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@0c4173a5
      
      Changelog-generator: Add parameter to include all integrated projects
      
      Before this, the changelog was generated on a given list of projects,
      all using the same branch.
      The new parameter now goes the the specified projects from the
      parameters, and detects all integrated projects into this.
      So normally you would specify one or two manifest projects, everything
      else is automatically added to the list.
      
      This also handles different branch names. As for example the kernel
      branches are different, the integration branch is used instead of the
      branch from the command line.
      d4da2a81
  12. Sep 12, 2024
  13. Aug 16, 2024
  14. Aug 06, 2024
  15. Aug 01, 2024
  16. Jul 29, 2024
  17. Jul 23, 2024
  18. Jul 11, 2024
  19. Jul 09, 2024
  20. Jul 05, 2024
  21. Jun 26, 2024
  22. Jun 04, 2024
  23. May 24, 2024
    • GitBot's avatar
      Integrate gitlab-ci/delete-infrastucture and 1 more · 04eaa7d5
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@01d6973b
      
      Scripts: Add script to delete all integration/ branches
      
      It happens that the integration branches are left over from provious
      runs of the pipeline, when MRs are closed without merging, for example.
      
      Also a bug in the gitlab-ci makes the pipeline fail, when an integration
      branch should be reused. The new scripts just deletes all integration
      branch in the given project tree without further checks.
      
      Needs to be run manually.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@c05acbe1
      
      Add scripts to setup a virtual python environment
      
      Use:
      ```
      cd script
      source setup_venv.sh
      ```
      to change to the venv.
      04eaa7d5
  24. May 23, 2024
  25. May 17, 2024
  26. May 13, 2024
  27. May 08, 2024
  28. May 02, 2024
  29. Apr 26, 2024
    • GitBot's avatar
      Integrate gitlab-ci/allow_failure · 60c6a412
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@6656c465
      
      CI: allow failure in new jobs 'handle_artifacts' and 'report-image-diff'
      
      It seems that these jobs are not yet completly errorsafe and we could
      ignore the failure without changing the build artifacts.
      60c6a412
    • GitBot's avatar
      Integrate gitlab-ci/keep_artifacts · d824bf68
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@de9851be
      
      ci: add a job to handle artifacts after merge
      
      In the latest commit in the manifest it often happens, that the pipeline
      does not contain the artifacts itself, but just a link to the pipeline of the MR.
      
      Added a python script with corresponding GitLab CI job to launch this script.
      The script searches for the latest pipelines for default branch in manifest repo,
      and then decides either to keep or delete artifacts for particular build.
      
      The build artifacts are kept for:
      - the latest commit
      - the last successful build
      - the tagged commits (e.g. "fngsystem/47.0", "kirkstone/20.0")
      d824bf68
Loading