Skip to content
Snippets Groups Projects
  1. Feb 21, 2024
  2. Feb 19, 2024
  3. Feb 09, 2024
  4. Feb 07, 2024
  5. Feb 01, 2024
  6. Jan 25, 2024
  7. Jan 22, 2024
  8. Jan 16, 2024
  9. Jan 08, 2024
  10. Dec 21, 2023
  11. Dec 19, 2023
  12. Nov 30, 2023
  13. Nov 20, 2023
  14. Nov 17, 2023
  15. Nov 16, 2023
  16. Nov 13, 2023
  17. Nov 10, 2023
    • Tobias Kahlki's avatar
      machines: Add new seco-nxp machine override · 0f380b0a
      Tobias Kahlki authored
      We need an additional override that has a higher prio than the ones from
      meta-freescale but still can be overridden by specific machine overrides
      (e.g. seco-mx8mp).
      The override is intended for vendor specific config files (e.g.
      weston.ini).
      0f380b0a
  18. Nov 07, 2023
  19. Nov 03, 2023
  20. Oct 27, 2023
  21. Oct 24, 2023
  22. Oct 23, 2023
  23. Oct 20, 2023
  24. Oct 19, 2023
    • GitBot's avatar
      Integrate gitlab-ci/reverse-pipeline-cancellation-order and 6 more · 3d6a1464
      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.
      3d6a1464
    • GitBot's avatar
      Integrate gitlab-ci/combine-confluence-pages-from-multiple-pipelines and 2 more · 81b008cd
      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.
      81b008cd
  25. Oct 16, 2023
  26. Oct 13, 2023
Loading