Skip to content
Snippets Groups Projects
  1. Feb 17, 2025
  2. Feb 07, 2025
  3. Feb 06, 2025
  4. Jan 25, 2025
  5. Jan 13, 2025
  6. Sep 24, 2024
  7. Aug 30, 2024
  8. Aug 16, 2024
  9. Jul 29, 2024
  10. Jul 11, 2024
  11. Apr 12, 2024
  12. Apr 03, 2024
  13. Mar 07, 2024
  14. Feb 27, 2024
  15. Jan 25, 2024
  16. Jan 24, 2024
  17. Jan 08, 2024
  18. Dec 06, 2023
  19. Sep 29, 2023
  20. Aug 15, 2023
  21. Aug 14, 2023
  22. Aug 08, 2023
  23. Aug 02, 2023
  24. Jun 07, 2023
  25. Jun 06, 2023
  26. May 31, 2023
    • Marcel Amirault's avatar
      Remove pipeline artifacts page · 120e2040
      Marcel Amirault authored
      Pipeline artifacts are not a thing that users interact with,
      they are internal components of test coverage visualization
      and do not need to be documented. We can keep some details
      about the data storage though.
      120e2040
  27. Apr 28, 2023
    • Cody Martin's avatar
      Switch to one line pytest coverage call · 2aa1831e
      Cody Martin authored and Marcel Amirault's avatar Marcel Amirault committed
      In the previous example, if the second line failed and returned a
      nonzero exit code, it would exit the job before executing the fourth
      line that generates the coverage.xml required for test coverage
      visualization. This is painful, given that users probably want to
      visualize line-by-line coverage when the tests fail even more than
      when it passes.
      
      Switch to a one-line call that runs the tests _and_ produces a
      coverage report. This enables test coverage visualization regardless
      of if the job passes or fails, even if other future jobs are skipped
      by this job's failure.
      2aa1831e
  28. Apr 12, 2023
  29. Mar 23, 2023
  30. Mar 15, 2023
  31. Feb 24, 2023
  32. Jan 23, 2023
  33. Nov 04, 2022
  34. Sep 21, 2022
  35. Jul 08, 2022
  36. Jun 22, 2022
  37. Jun 13, 2022
  38. Jun 03, 2022
  39. May 26, 2022
Loading