Skip to content
Snippets Groups Projects
  1. Mar 08, 2022
  2. Feb 17, 2022
  3. Feb 15, 2022
  4. Feb 14, 2022
  5. Feb 10, 2022
  6. Feb 07, 2022
  7. Feb 03, 2022
  8. Feb 02, 2022
  9. Jan 28, 2022
  10. Jan 27, 2022
  11. Jan 17, 2022
  12. Jan 04, 2022
  13. Jan 03, 2022
  14. Dec 30, 2021
  15. Dec 24, 2021
  16. Dec 23, 2021
  17. Dec 21, 2021
  18. Dec 15, 2021
  19. Dec 10, 2021
  20. Dec 05, 2021
  21. Dec 03, 2021
  22. Dec 02, 2021
  23. Nov 30, 2021
  24. Nov 24, 2021
  25. Nov 23, 2021
    • Emanuele Aina's avatar
      ostree-commit: Parametrize ref-binding on osname · 8f7b913d
      Emanuele Aina authored
      
      Make the ref-bindings work automatically for downstreams by
      parametrizing them on the `$osname` template variable instead of
      hardcoding `apertis`.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      8f7b913d
    • Emanuele Aina's avatar
      Do not upload artifacts on secondary branches to save resources · c36b7fdc
      Emanuele Aina authored
      
      When there are many work-in-progress branches at the same time they all
      get uploaded to the test area, increasing noticeably the storage
      consumption on the server.
      
      In addition, when multiple branches are in progress it is not uncommon
      to rebase them frequently, which causes additional builds and thus an
      additional burden on the storage server.
      
      On top of that, each of those builds gests submitted to LAVA, where the
      available DUTs are already a scarce resource.
      
      Save some storage and device time on LAVA by **not** uploading from
      secondary branches (that is, anything except the `apertis/*` branches).
      
      If it is desirable to really upload and submit to LAVA from secondary
      branches, set the following CI variables when triggering a pipeline:
      
      * `UPLOAD_ARTIFACTS=1`
      * `SUBMIT_LAVA_JOBS=1`
      
      When not uploaded to the storage server, artifacts are still available
      from GitLab since they get captured as pipeline artifacts, expiring
      after a day just like on the storage server where a daily job cleaned
      them up.
      
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      c36b7fdc
  26. Nov 22, 2021
Loading