Skip to content
Snippets Groups Projects
  1. Mar 12, 2025
  2. Mar 10, 2025
  3. Feb 11, 2025
  4. Jan 30, 2025
    • Marc-Oliver Westerburg's avatar
      LM73: fix temperature sensor on SANTARO/SANTOKA · fa1aaf9c
      Marc-Oliver Westerburg authored
      For SANTARO/SANTOKA the board temperature sensor was declared as
      "national,lm75" in the device-tree resulting in the LM73 sensor
      equipped on these system being treated as LM75 and therefore giving
      wrong temperature read-outs.
      
      This patch declares the temperature correctly as "national,lm73", which
      results in proper temperature read-outs.
      
      YT-348
      fa1aaf9c
  5. Jan 14, 2025
  6. Jan 08, 2025
  7. Nov 27, 2024
  8. Nov 18, 2024
  9. Nov 11, 2024
    • GitBot's avatar
      Integrate gitlab-ci/yt-260-restrict-edit-rights-on-confluence-release-page · 8995f298
      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.
      8995f298
  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 · 58c11bd5
      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.
      58c11bd5
  14. Sep 20, 2024
    • GitBot's avatar
      Integrate gitlab-ci/changelog-generator-all-projects-YT-256 and 3 more · d8bc0e60
      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.
      d8bc0e60
  15. Sep 12, 2024
  16. Aug 16, 2024
  17. Aug 06, 2024
  18. Aug 01, 2024
  19. Jul 29, 2024
    • Dmitry Petrov's avatar
      panel-dt: switch sel6-8-gpio to low in unprepare · 4f570f56
      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.
      4f570f56
    • GitBot's avatar
      Integrate gitlab-ci/YT-180-generate-firmware-package-not-working-for-fngsystem · c7b4ffc1
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@a7e07f19
      
      YT-180 Generation of the firmware package failed due to a typo
        in the code that checks of existance of the variable.
        What caused  TypeError: unhashable type: 'list'
      c7b4ffc1
    • GitBot's avatar
      Integrate gitlab-ci/PBB-32-flash-n-go-deploy-folder-no-suffix · f2705dfb
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@7bd78810
      
      PBB-32 Fix suffix addition in FNGo pipeline for custom projects
       due to an issue in GitLab where escaped variables are not correctly
       passed to child pipelines, a workaround is required.
       As a result, we use raw variables.
       The DEFERRED_RELEASE_VERSION variable was introduced for this purpose.
       However, for custom builds, we have an additional place where we modify
       the DEFERRED_RELEASE_VERSION variable to add a suffix.
       Therefore, extra interim variables need to be added to handle the workaround
       and ensure we get the raw variable in the end.
      f2705dfb
  20. Jul 23, 2024
  21. Jul 11, 2024
  22. Jul 09, 2024
  23. Jul 08, 2024
  24. Jul 05, 2024
  25. Jun 26, 2024
  26. Jun 03, 2024
  27. May 24, 2024
    • GitBot's avatar
      Integrate gitlab-ci/delete-infrastucture and 1 more · ae892ce1
      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.
      ae892ce1
  28. May 23, 2024
    • GitBot's avatar
      Integrate gitlab-ci/fix_collect_confluence · a63e43bb
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@58554035
      
      scripts:release_info: Deep copy dict in merge_variables
      
      Without the deep copy, the merge operation manipulates the dict it is
      storing the new values in.
      a63e43bb
    • GitBot's avatar
      Integrate gitlab-ci/report-image-diff-rework and 1 more · 407e9e5a
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@bd4caeae
      
      report_image_diff: rework variables extraction
      
      The current solution makes too much assumptions about the pipeline and needs
      to reimplement some of the gitlab yaml interpretion.
      
      The new version of the script extracts MACHINE and DISTRO from the jobs themselves:
      - MACHINE is part of the build job name ("build-$MACHINE");
      - DISTRO is printed by bitbake and can be found in build log.
      
      Typos
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@cbf168eb
      
      build:credentials: Fix error when storing credentials in cache
      
      The credentials helper wasn't storing the credentials in the cache.
      Seemingly, the echo added whitespaces at the beginning of the lines
      which can't be interpreted by the git credential approve command.
      Also the USERNAME was renamed to TOKEN_USER because the variable is
      already filled with the system users name.
      407e9e5a
  29. May 13, 2024
  30. May 08, 2024
  31. May 02, 2024
  32. Apr 26, 2024
Loading