Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: specify exact paths and better names for gitlab artifacts #6483

Closed
wants to merge 2 commits into from

Conversation

UdjinM6
Copy link

@UdjinM6 UdjinM6 commented Dec 12, 2024

Issue being fixed or feature implemented

We include too many files in artifacts on build ci step, some of which (*.a and *.o) can be pretty heavy. This was ok-ish for some time but artifacts size is getting closer to the limit and even starts to cause issues, see #6462.

What was done?

Specify exact files that are needed for functional tests (test ci step) and for users who wants to get binaries from artifacts. Also, change artifacts name to make it easier to distinguish them when you get a few of them from the same pipeline - build-arm-linux.zip, build-linux64.zip etc. instead of binaries.zip, binaries (1).zip etc., same for depends.

As a result the size of tsan artifacts for example is down from 508MB in 6462 to 116MB in this PR (or 78MB if we exclude logs 47ae9a4).

How Has This Been Tested?

Breaking Changes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation
  • I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

@UdjinM6 UdjinM6 added this to the 22.1 milestone Dec 12, 2024
@UdjinM6 UdjinM6 marked this pull request as draft December 12, 2024 18:08
@UdjinM6 UdjinM6 force-pushed the ci_exact_paths branch 3 times, most recently from e3d0fa6 to f5ef582 Compare December 12, 2024 20:36
Copy link

This pull request has conflicts, please rebase.

@UdjinM6 UdjinM6 removed this from the 22.1 milestone Dec 14, 2024
PastaPastaPasta added a commit that referenced this pull request Dec 14, 2024
…downloaded files

a191c09 ci: better names for artifacts (UdjinM6)
3984a49 ci: exclude `*.a` and `*.o` files from artifacts (UdjinM6)

Pull request description:

  ## Issue being fixed or feature implemented
  We include too many files in artifacts on `build` ci step, some of which (`*.a` and `*.o`) can be pretty heavy. This was ok-ish for some time but artifacts size is getting closer to the limit and even starts to cause issues, see #6462.

  ## What was done?
  Exclude `*.a` and `*.o` files from artifacts. Also, change artifacts name to make it easier to distinguish them when you get a few of them from the same pipeline - `build-arm-linux.zip`, `build-linux64.zip` etc. instead of `binaries.zip`, `binaries (1).zip` etc., same for `depends`.

  A simpler alternative to #6483

  As a result the size of tsan artifacts for example is down from 508MB in 6462 to 154MB in this PR.

  ## How Has This Been Tested?

  ## Breaking Changes

  ## Checklist:
  - [ ] I have performed a self-review of my own code
  - [ ] I have commented my code, particularly in hard-to-understand areas
  - [ ] I have added or updated relevant unit/integration/functional/e2e tests
  - [ ] I have made corresponding changes to the documentation
  - [ ] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_

ACKs for top commit:
  PastaPastaPasta:
    utACK a191c09
  kwvg:
    utACK a191c09

Tree-SHA512: eb3029c95a11546958d34ad284f4eb600b6113a2cabb885f7381afd16696f51da7eaf1677a1cdfec53311838c6845bb1c2c7c98f0ae112294b33f6ab6c66c500
Copy link

This pull request has conflicts, please rebase.

@UdjinM6
Copy link
Author

UdjinM6 commented Dec 14, 2024

superseded by #6487

@UdjinM6 UdjinM6 closed this Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant