Skip to content
Snippets Groups Projects
  1. Sep 04, 2024
  2. Jul 13, 2024
  3. Jun 25, 2024
    • Robert Schmidt's avatar
      Update cross-compilation builder to Ubuntu 22 · 199f8c21
      Robert Schmidt authored
      Update instructions and CI for cross-compilation on Ubuntu 22.
      Note that for the dockerfile, we use egrep -L which has changed and does
      not exit with code 0 on no match. Instead, use -vqz to invert return
      code (0 if nothing found, otherwise 1).
      199f8c21
    • Robert Schmidt's avatar
      Upgrade CI images to Ubuntu 22 · 94497435
      Robert Schmidt authored
      This updates all images in the CI to Ubuntu 22. It also updates
      corresponding documentation. Remove python(2) from the image, as it is
      not needed. Update documentation.
      
      It seems that the gcc coming in Ubuntu 22 does not like
      stack-protector-strong, so remove it as well.
      
      Since we compile Flexric, which does not support Ubuntu 22's default
      gcc-11 (it hits a compile bug), switch to gcc-12 manually.
      
      Since we update the compiler, we also need to be careful to use the right
      address sanitizer version (which is bundled with the compiler version).
      To avoid a reinstallation of the wrong asan version in target images, we
      modify Ubuntu 22 targets to copy libasan from the base image. This is necessary
      since we use update-alternative in the base image, but we don't want to
      install compilers in the target images to use update-alternatives to
      install the right asan version... This should be undone when switching
      to Ubuntu 24 in the future, as it will have a newer default gcc version,
      such that we don't need to update the compile in the first place.
      
      Upgrade libpython in lteUE for U22 upgrade to make it compatible with
      UHD.
      94497435
  4. Jun 13, 2024
  5. Jun 05, 2024
  6. Jun 03, 2024
    • Robert Schmidt's avatar
      CI DeployObject: don't grep, just give service name · 0077d219
      Robert Schmidt authored
      With the capabilities now given as part of this MR, it happens that when
      checking the "docker compose config", the container_name might not be
      close to the service name. Something like
      
        service:
          cap_drop:
            ...
          cap_add:
            ...
          container_name:
      
      This is inconvenient, as the previous grep for the service name + 3
      lines might not cover the service name. To circumvent this, give the
      service name directly in "docker compose config". (no clue why it has
      not been done like this from the start)
      0077d219
    • Robert Schmidt's avatar
      BuildUnitTests: need to use ran-base:ci-temp if changes in ran-base · 37421c3f
      Robert Schmidt authored
      Use correct baseTag for Unit Tests build in execution:
      - if build_helper or othe files changed, which would trigger rebuild of
        ran-base, use the corresponding ci-temp tag
      - use that tag consistently afterwards
      37421c3f
  7. Apr 18, 2024
    • Jaroslava Fiedlerova's avatar
      CI: Modification of log collection in UndeployObject() · e3547dfb
      Jaroslava Fiedlerova authored
      After the recent update of matix, collected logs contain color codes
      and we did not find the way to switch them completely off.
      Replacement of "docker compose logs" by "docker logs" resolves this
      issue. This commit includes changes related to "docker logs" usage.
      e3547dfb
  8. Apr 08, 2024
  9. Mar 27, 2024
  10. Mar 22, 2024
  11. Mar 08, 2024
  12. Mar 05, 2024
  13. Feb 08, 2024
  14. Feb 05, 2024
  15. Jan 29, 2024
  16. Jan 24, 2024
  17. Nov 29, 2023
  18. Nov 10, 2023
  19. Oct 25, 2023
  20. Oct 04, 2023
  21. Sep 18, 2023
    • Raphael Defosseux's avatar
      fix(ci): properly removing docker volumes · 29b4e64d
      Raphael Defosseux authored
      
      Laurent noticed it on one of his MR and confirmed with him:
        -- Volumes have be created the 1st time they ran on avra on July 7th
        -- Volumes were created with not only the raw files but also the nr-softmodem executable
      
      Solution: two-fold:
        1. using the `docker-compose down -v` syntax, the volume is deleted automatically
        2. I added redundancy with the custom command to remove the used volume
      
      Signed-off-by: default avatarRaphael Defosseux <raphael.defosseux@eurecom.fr>
      29b4e64d
  22. Sep 14, 2023
Loading