Skip to content

Use XZ compression for RPM packages

What does this MR do?

This is a follow-on to !7128 (merged), where we enabled XZ compression for DEB packages. Unfortunately, Omnibus didn't do threaded compression for RPM packages because of the way it was setting _binary_payload. That was causing XZ compression in particular to take 2-3 times longer than GZip, so we could not merge that change at the same time. With omnibus!48 (merged) merged, Omnibus will use threaded compression for RPM by default and we can enable XZ compression for RPM packages as well.

Related issues

Closes #8222 (closed)

Test Plan

This tests basic post-install functionality:

  • Package installs on target platform
  • Configure gitlab to use gitlab.example.com in /etc/gitlab/gitlab.rb
  • Run sudo gitlab-ctl reconfigure
  • Connect to gitlab.example.com and log in as root
  • Create a new group
  • Create an empty project with a README in the new group
  • Create a test issue in the project

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
  • Documentation created/updated.
  • Tests added.
  • Integration tests added to GitLab QA.
  • Equivalent MR/issue for the GitLab Chart opened.
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Ryan Egesdahl

Merge request reports