Skip to content
Snippets Groups Projects
  1. Oct 30, 2024
  2. Aug 16, 2024
  3. Aug 06, 2024
  4. Aug 01, 2024
  5. Jul 29, 2024
  6. Jul 23, 2024
  7. Jul 11, 2024
  8. Jul 09, 2024
  9. Jul 05, 2024
  10. Jun 26, 2024
  11. May 24, 2024
    • GitBot's avatar
      Integrate gitlab-ci/delete-infrastucture and 1 more · 0e47c442
      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.
      0e47c442
  12. May 23, 2024
    • GitBot's avatar
      Integrate gitlab-ci/fix_collect_confluence · 86f24c30
      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.
      86f24c30
    • GitBot's avatar
      Integrate gitlab-ci/report-image-diff-rework and 1 more · 8d7a2816
      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.
      8d7a2816
  13. May 13, 2024
  14. May 08, 2024
  15. May 02, 2024
  16. Apr 26, 2024
    • GitBot's avatar
      Integrate gitlab-ci/allow_failure · ea6e3a0a
      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.
      ea6e3a0a
    • GitBot's avatar
      Integrate gitlab-ci/keep_artifacts · 1e173afd
      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")
      1e173afd
  17. Apr 25, 2024
    • GitBot's avatar
      Integrate gitlab-ci/report_image_changes_in_mr · a054bc58
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@1299a9d6
      
      CI: add "report-image-diff" job
      
      Add a python script and a GitLab CI job to run it. The job is triggered
      when the build is complete.
      
      The script retrieves build artifacts for the default/main branch
      (currently "kirkstone") in the manifest repo and build artifacts
      for the integration branch of merge request.
      
      After that, it compares those builds and creates a summary of the overall
      changes. In particular:
      - size of compressed artifacts (artifacts.zip)
      - size of built image
      - difference between manifest files
      
      The summary is reported to stdout and as a comment to the merge request.
      Each run of the pipeline means removing the old summary comment and
      creating a new one when the build is finished.
      a054bc58
  18. Apr 19, 2024
  19. Apr 11, 2024
  20. Apr 08, 2024
  21. Mar 20, 2024
  22. Mar 19, 2024
  23. Mar 18, 2024
    • GitBot's avatar
      Integrate gitlab-ci/bb-recipe-linter and 1 more · 762fff44
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@44000de1
      
      Check bitbake recipes with linter
      
      The job checks bitbake recipes added/updated in MR using the
      oelint-adv tool (https://github.com/priv-kweihmann/oelint-adv).
      
      .oelint.json is a rulefile, created with the command
      "oelint-adv --print-rulefile". It can be used during development.
      It contains default rules for now, but will probably be customized later.
      
      To get the list of changed files in MR, we adjusted the GIT_DEPTH variable.
      The new value is 50, which should be fine for getting MR changes,
      and still small enough to keep checkout fast for large projects.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@9d9574d1
      
      convert_md2html: fix text duplication
      
      Fix the problem introduced by commit 4f06516 "convert_md2html: fix id
      fields for headings".
      
      The text converted from markdown was written twice to the HTML document.
      762fff44
  24. Mar 06, 2024
  25. Mar 04, 2024
  26. Feb 23, 2024
  27. Feb 19, 2024
  28. Dec 21, 2023
  29. Nov 20, 2023
  30. Nov 17, 2023
  31. Nov 07, 2023
  32. Oct 23, 2023
  33. Oct 20, 2023
  34. Oct 19, 2023
    • GitBot's avatar
      Integrate gitlab-ci/reverse-pipeline-cancellation-order and 6 more · d0b58876
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@3697b4ea
      
      cancel_pipelines: reverse order of cancellation
      
      Cancel parent pipeline first before cancelling its children in order not
      to have failed parent pipelines (trigger jobs are failed if their
      downstream pipeline is cancelled).
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@5f4ca2fb
      
      cancel_pipelines: list actually cancelled (child-)pipelines
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@c80cba84
      
      Cancel all pipelines on newer commit
      
      We already canceled running pipelines before. Gitlab, however, might
      have already canceled previous pipelines automatically, but without
      canceling their child pipelines.
      Remove the "running" status filter when cancelling pipelines, so that
      also already cancelled pipelines will be included.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@84eb6e22
      
      Revert "Cancel all pipelines on newer commit"
      
      This reverts commit f7582b74e7c565d55bb8a0315fe75c4ab4385fa2.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@f7582b74
      
      Cancel all pipelines on newer commit
      
      We already canceled running pipelines before. Gitlab, however, might
      have already canceled previous pipelines automatically, but without
      canceling their child pipelines.
      Extend the mechanism now to cancel all pipelines up to and including
      "running" as well as "canceled" states.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@0ec55c07
      
      Fix list() call in update_submodule
      
      Here we don't just iterate over the results, so we have to use
      "all=True" instead of "as_list=False". See previous commit for
      explaination.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@4b3a517e
      
      Make sure to get all items on Gitlab list() calls
      
      The list() call on Gitlab classes uses pagination per default. If the
      number of items exceeds a certain limit, we only get a part of the
      results. We can pass "all=True" to the calls in order to disable
      pagination and get all results.
      If we're looping over the items, though, the recommended way of getting
      them is to use a generator object, which works calling list() with
      "as_list=False". See documentation for reference:
      
      https://python-gitlab.readthedocs.io/en/v2.10.1/api-usage.html#pagination
      
      Note: the "as_list" argument is deprecated in newer versions of the
      python-gitlab library, in favor of the newer "iterator=True":
      https://python-gitlab.readthedocs.io/en/v3.6.0/changelog.html#feature
      We are using v2.10.1 of the library, though, so this commit also updates
      calls using the new way, which is not working with our version.
      d0b58876
    • GitBot's avatar
      Integrate gitlab-ci/combine-confluence-pages-from-multiple-pipelines and 2 more · d0b62ac1
      GitBot authored
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@c292d144
      
      Confluence: combine data from parallel child pipelines
      
      We deploy Yocto image and SDK in different pipelines, which both have
      their Confluence jobs with the same Confluence target. Previously these
      pipelines have been independent, so that running the Confluence job in
      one of them would overwrite the Confluence page if it has been run in
      the other pipeline before. Hence we could either have the image files or
      the SDK files in the Confluence page.
      Combine these now by checking for other parallel child pipelines with
      the same Confluence configuration, so that running the Confluence jobs
      in the Yocto pipeline also includes the information from the SDK build
      and vice versa.
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@53106170
      
      Fix ci-test SDK version
      
      --
      
      Commit: seco-ne/yocto/infrastructure/gitlab-ci@d6d4ab61
      
      Fix ci-test SDK download
      
      Since the implementation of multiple child pipelines we cannot use the
      previous artifacts download links anymore specifying tag and job name,
      because the jobs for image build and SDK build are equal. Use direct
      download links instead via job number.
      d0b62ac1
Loading