CI: Skip downloading artifacts of previous jobs

Philipp Hahnrequested to merge
gitlab-community/gitlab-org/gitlab-runner:phahn/ci-skip-artifacts into main

What does this MR do?

CI: Skip downloading artifacts of previous jobs

The rebase jobs runs latest and thus downloads artifacts from all previous jobs and stages, which are not even used. Looking at https://gitlab.com/gitlab-org/gitlab-runner/-/jobs/11151081441 shows, that the job rebase on main spent 08:35:43-08:45:36 = 10 minutes on downloading, while the actual rebase was done in 08:46:44-08:46:51 = 7 seconds.

Total downloaded artifacts size: approximately 15.9 GB Based on the build log, here's the summary of downloaded artifacts:
  1. helper images (alpine, alpine-pwsh, ubuntu, ubuntu-pwsh, ubi-fips): 2.21 GB
  2. helper images (windows-nanoserver-ltsc2019, windows-servercore-ltsc2019): 2.66 GB
  3. helper images (windows-nanoserver-ltsc2022, windows-servercore-ltsc2022): 2.73 GB
  4. prebuilt helper images: 1.54 GB
  5. prebuilt helper images windows 2019: 2.28 GB
  6. prebuilt helper images windows 2022: 2.31 GB
  7. runner images: 1.13 GB
  8. binaries: 523.95 MB
  9. clone test repo: 34.21 KB
  10. rpm verify fips: 1.54 KB
  11. code_quality: 226 B
  12. gemnasium-dependency_scanning: 8.85 KB
  13. gitlab-advanced-sast: 13.48 KB
  14. unit test: 8.83 MB
  15. integration test 1/4: 1.01 MB
  16. integration test 2/4: 861.34 KB
  17. integration test 3/4: 971.91 KB
  18. integration test 4/4: 891.27 KB
  19. integration test with race 1/4: 1.01 MB
  20. integration test with race 2/4: 858.49 KB
  21. integration test with race 3/4: 969.71 KB
  22. integration test with race 4/4: 888.68 KB
  23. fuzz variable mask: 58.44 KB
  24. windows 1809 unit tests 1/2: 11.05 MB
  25. windows 1809 unit tests 2/2: 8.57 MB
  26. windows 21H2 unit tests 1/2: 11.05 MB
  27. windows 21H2 unit tests 2/2: 8.57 MB
  28. windows 1809 integration tests 1/4: 1.01 MB
  29. windows 1809 integration tests 2/4: 861.77 KB
  30. windows 1809 integration tests 3/4: 974.22 KB
  31. windows 1809 integration tests 4/4: 892.15 KB
  32. windows 21H2 integration tests 1/4: 1.01 MB
  33. windows 21H2 integration tests 2/4: 861.72 KB
  34. windows 21H2 integration tests 3/4: 974.61 KB
  35. windows 21H2 integration tests 4/4: 892.22 KB
  36. test coverage report: 33.92 MB
  37. package-deb: [deb64]: 24.37 MB
  38. package-deb: [debArm64]: 44.09 MB
  39. package-deb: [deb32]: 22.47 MB
  40. package-deb: [debArm32]: 45.51 MB
  41. package-deb: [debIbm]: 44.47 MB
  42. package-deb: [debRiscv64]: 23.34 MB
  43. package-rpm: [rpm64]: 24.40 MB
  44. package-rpm: [rpmArm64]: 44.10 MB
  45. package-rpm: [rpm32]: 22.46 MB
  46. package-rpm: [rpmArm32]: 45.53 MB
  47. package-rpm: [rpmIbm]: 44.48 MB
  48. package-rpm: [rpmRiscv64]: 23.33 MB
  49. package-rpm: [rpmFips]: 76.00 MB
  50. package-helpers: 1.02 GB
  51. bleeding edge docker images: 2.96 KB
  52. integration kubernetes exec legacy: 3.62 KB
  53. integration kubernetes attach: 5.18 KB
  54. integration kubernetes: 2.71 KB
  55. destroy integration kubernetes: 5.18 KB
  56. package test variables: 307 B

Total downloaded artifacts size: approximately 15.9 GB

Improve pipeline efficiency and disable downloading dependencies and caches; see https://docs.gitlab.com/ci/yaml/#dependencies.

Signed-off-by: Philipp Matthias Hahn pmhahn@pmhahn.de

Why was this MR needed?

Just a performance improvement while waiting for https://gitlab.com/gitlab-org/gitlab-runner/-/jobs/11151081441 triggered by !5799 (merged)

What's the best way to test this MR?

@ajwalker may know, how he triggered that pipeline.

What are the relevant issue numbers?

None

Edited by 🤖 GitLab Bot 🤖

Merge request reports