Skip to content
Snippets Groups Projects
  1. Mar 14, 2025
  2. Mar 12, 2025
  3. Mar 10, 2025
  4. Feb 11, 2025
  5. Jan 09, 2025
  6. Jan 08, 2025
  7. Nov 18, 2024
  8. Nov 11, 2024
    • GitBot's avatar
      Integrate gitlab-ci/yt-260-restrict-edit-rights-on-confluence-release-page · d328c2ee
      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.
      d328c2ee
  9. Nov 07, 2024
  10. Oct 14, 2024
  11. Oct 10, 2024
  12. Oct 01, 2024
  13. Sep 30, 2024
    • GitBot's avatar
      Integrate gitlab-ci/yt-160-gitlab-ci-integration-often-fails-on-merge-yocto-step · 8960265b
      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.
      8960265b
  14. Sep 20, 2024
    • GitBot's avatar
      Integrate gitlab-ci/changelog-generator-all-projects-YT-256 and 3 more · 59a4d709
      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.
      59a4d709
  15. Sep 12, 2024
  16. Sep 09, 2024
  17. Aug 23, 2024
  18. Aug 16, 2024
  19. Aug 06, 2024
  20. Aug 05, 2024
    • Dmitry Petrov's avatar
      panel-dt/panel-lvds: switch sel6-8-gpio to low in unprepare · 9ad2bc3d
      Dmitry Petrov authored and Jonas Höppner's avatar Jonas Höppner committed
      There is an issue with a display showing artifacts after leaving the display
      blank for some time. If sel6_8 line stays high during the power-off of the
      display, the display gets side-powered by the sel6_8 line. And the power
      sequence during the next power up does not reset the display in a good state.
      
      So switch the sel6_8 gpio to low, when the VDD-LCD is powered of, and enable it
      to the correct state, just before the VDD-LCD is powered on again.
      
      (cherry picked from commit 4f570f563b1ea85d901b8db98af6ad629c4aa1ba)
      
      sel68
      9ad2bc3d
  21. Aug 01, 2024
  22. Jul 29, 2024
  23. Jul 23, 2024
  24. Jul 11, 2024
  25. Jul 09, 2024
  26. Jul 08, 2024
  27. Jul 05, 2024
  28. Jul 02, 2024
  29. Jun 26, 2024
  30. Jun 13, 2024
  31. May 27, 2024
Loading