Remove some binaries from setup-test-env artifacts
Context
Follow-up of #442029 (comment 1780803004).
The setup-test-env
CI job contains several binaries, and those take up more than 200MB (this is thanks to the optimization done in #442029 (comment 1780803004), as it used to take more than 300MB):
tmp/tests/gitlab-workhorse/gitlab-zip-cat
tmp/tests/gitlab-workhorse/gitlab-zip-metadata
tmp/tests/gitlab-workhorse/gitlab-workhorse
tmp/tests/gitlab-workhorse/gitlab-resize-image
tmp/tests/gitlab-elasticsearch-indexer/bin/gitlab-elasticsearch-indexer
tmp/tests/gitaly/_build/bin/gitaly-git-http-backend-v2.43
tmp/tests/gitaly/_build/bin/praefect
tmp/tests/gitaly/_build/bin/gitaly-git-remote-http-v2.43
tmp/tests/gitaly/_build/bin/gitaly-lfs-smudge
tmp/tests/gitaly/_build/bin/gitaly-ssh
tmp/tests/gitaly/_build/bin/gitaly-debug
tmp/tests/gitaly/_build/bin/gitaly-hooks
tmp/tests/gitaly/_build/bin/gitaly-gpg
tmp/tests/gitaly/_build/bin/gitaly-blackbox
tmp/tests/gitaly/_build/bin/gitaly-wrapper
tmp/tests/gitaly/_build/bin/gitaly
tmp/tests/gitaly/_build/bin/gitaly-backup
tmp/tests/gitaly/_build/bin/gitaly-git-v2.43
Goal
- Check whether all of those binaries are used in CI/CD jobs
- Validate with the responsible group/team whether we could remove those from the artifacts
- This would be to verify that this artifact isn't used in any other cross-project pipeline, breaking other project's pipelines.
How to know which binaries to remove?
From @splattael in this comment:
We could go ahead and randomly remove binaries like
gitaly-debug
andgitlay-ssh
and see if all specs (including QA) are passing