- Feb 24, 2023
-
-
Balasankar 'Balu' C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
- Dec 13, 2022
-
-
Stan Hu authored
See https://bugs.ruby-lang.org/issues/19161
-
- Dec 02, 2022
-
-
Stan Hu authored
These versions includes a security fix and some minor fixes: * https://www.ruby-lang.org/en/news/2022/11/24/ruby-2-7-7-released/ * https://www.ruby-lang.org/en/news/2022/11/24/ruby-3-0-5-released/ Changelog: changed
-
- Nov 23, 2022
-
-
Balasankar 'Balu' C authored
Merge branch 'security-ruby-2.7.6' into 'master' See merge request gitlab-org/security/omnibus-gitlab!262 Changelog: security
-
- Oct 07, 2022
-
-
Balasankar 'Balu' C authored
Related https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6286 Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
- Sep 23, 2022
-
-
Balasankar 'Balu' C authored
Compile jemalloc with Ruby by default See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/6363 Merged-by:
Balasankar 'Balu' C <balasankar@gitlab.com> Approved-by:
Balasankar 'Balu' C <balasankar@gitlab.com> Co-authored-by:
Stan Hu <stanhu@gmail.com>
-
- Sep 19, 2022
-
-
Stan Hu authored
For years the Ruby interpreter has been dynamically loaded with jemalloc by using `LD_PRELOAD` to replace the system's malloc calls. While this makes it possible to disable jemalloc, some anti-virus scanners flag this behavior and abort the Ruby interpreter. Since jemalloc has: 1. Significantly improved memory usage 2. Is compiled with the default for Cloud Native GitLab images 3. Is compiled with the default for all GitLab CI images We should enable by this default and deprecate the configuration variable. To do this, we need to install all jemalloc files, not just the library and binary files. We also need to pass `-Wl,--no-as-needed` as a linker argument due to https://bugs.ruby-lang.org/issues/18409. Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/4357 Changelog: changed
-
- Sep 15, 2022
-
-
Stan Hu authored
If Ruby is compiled against Amazon Linux's OpenSSL v1.0.2, `Digest::MD5.new` fails with: ``` md5_dgst.c(82): OpenSSL internal error, assertion failed: Digest MD5 forbidden in FIPS mode! ``` However, this doesn't happen on RedHat or Ubuntu FIPS because the OpenSSL `MD5_Init()` call isn't disabled in their OpenSSL v1.1 FIPS libraries. Instead, it is disabled via the `EVP_DigestInit_ex()` call, which is why `OpenSSL::Digest::MD5.new` fails but `Digest::MD5.new` works. In either case, we should just use the Ruby MD5 implementation until Chef completely removes the use of MD5. Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/7182 Changelog: fixed
-
- Aug 04, 2022
-
-
Balasankar 'Balu' C authored
Remove upstream patch for RHEL 5 and Ruby 2.1/2.2 from ruby See merge request gitlab-org/omnibus-gitlab!6247
-
- Aug 03, 2022
-
-
Takuya Noguchi authored
In the upstream, this was removed in 2018: https://github.com/chef/omnibus-software/pull/965 Signed-off-by:
Takuya Noguchi <takninnovationresearch@gmail.com>
-
Takuya Noguchi authored
Red Hat Enterprise Linux (RHEL) 5 reached end of extented life-cycle support aka ELS by Red Hat in Nov 2020. Partially porting from: https://github.com/chef/omnibus-software/pull/1088 Signed-off-by:
Takuya Noguchi <takninnovationresearch@gmail.com>
-
- Jul 15, 2022
-
-
Stan Hu authored
The global setting may not get restored from the cache, so let's just duplicate this for now where we need it. Changelog: changed
-
- Jul 14, 2022
-
-
Stan Hu authored
Previously Gitaly's `bundle install` installed a native gem for Nokogiri, even though GitLab Rails already installed the Ruby platform version. `bundle config set <value>`by default only sets the value locally, so the `force_ruby_platform` setting only affected GitLab Rails. Due to `rack-compiler-dock` building native gems on ARM64 with a Ubuntu 20.04-based image instead of `manylinux` (https://github.com/pypa/manylinux) as x86 builds do, ARM64 native gems depend on glibc v2.29. RedHat ARM64 platforms usually use an older version, such as v2.28 in CentOS 8. Note that Omnibus depends on a number of projects that may use native gems: - GitLab Rails - Gitaly - gitlab-exporter - MailRoom Currently only Nokogiri v1.13 appears to ship an ARM64 native gem. However, if some gem does the same, such as `pg`, then we'd hit similar issues with `gitlab-exporter`. To avoid this, set `force_ruby_platform` to `true` globally. Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/367444 Changelog: fixed
-
- Apr 11, 2022
-
-
Stan Hu authored
In the Ubuntu 18.04 FIPS builds, currently `OpenSSL.fips_mode` is `false`, which prevents GitLab from entering FIPS mode. Even though these builds properly link against the FIPS-enabled system OpenSSL, this flag is `false` because Ruby compiles out the dynamic `FIPS_mode()` checks (https://wiki.openssl.org/index.php/FIPS_mode()) unless the `OPENSSL_FIPS` macro is defined. In RedHat, `OPENSSL_FIPS` is always defined in `/usr/include/openssl/opensslconf-x86_64.h`, but this is not the case for Ubuntu. On non FIPS-systems, `FIPS_mode()` should return 0 (not available), so this compile-time guard should not be necessary. For now, we only enable it for builds that link against the system SSL. Relates to https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/6775 Changelog: fixed
-
- Dec 20, 2021
-
-
DJ Mountney authored
-
- Dec 03, 2021
-
-
DJ Mountney authored
-
- Sep 15, 2021
-
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
- Sep 02, 2021
-
-
Balasankar 'Balu' C authored
Update Ruby to 2.7.4 See merge request gitlab-org/omnibus-gitlab!5545
-
- Aug 17, 2021
-
-
Matthias Kaeppler authored
Changelog: changed
-
- Aug 18, 2021
-
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankar@gitlab.com>
-
- Jul 12, 2021
-
-
Robert Marshall authored
-
- Jan 21, 2021
-
-
Kamil Trzciński authored
This includes backported patch from https://github.com/ruby/ruby/pull/3978.
-
- Oct 08, 2020
-
-
Stan Hu authored
Update RubyGems to v3.1.4 Part of https://gitlab.com/groups/gitlab-org/-/epics/2380
-
- Jun 17, 2020
-
-
Stan Hu authored
Calls to the `copy_file_range()` system call on recent RedHat kernels now fail with `EOPNOTSUP` instead of `ENOSYS`, which breaks any use of `IO.copy_stream` (e.g. used by CarrierWave) if NFS is used. Ruby attempts to detect whether the kernel supports this system call, but the detection mechanism only checks whether this system call is defined, not whether it is actually supported. We manually patch this to disable the `copy_file_range()`. Relates to: 1. https://bugs.ruby-lang.org/issues/16965 2. https://gitlab.com/gitlab-org/gitlab/-/issues/218999 3. https://bugzilla.redhat.com/show_bug.cgi?id=1783554
-
- May 18, 2020
-
-
Dustin Collins authored
-
- Mar 24, 2020
-
-
Igor Wiedler authored
-
- Jan 02, 2020
-
-
Balasankar "Balu" C authored
Signed-off-by:
Balasankar "Balu" C <balasankarc@autistici.org>
-
- Jul 31, 2019
-
-
Ian Baum authored
* Add rubocop-rails and rubocop-performance gems * Update renamed gems in .rubocop.yml * Auto-correct where possible * Manually fix remaining gems
-
- Mar 20, 2019
-
-
Stan Hu authored
-
- Oct 24, 2018
-
-
- Oct 19, 2018
-
-
- Sep 05, 2018
-
-
Ian Baum authored
-
- May 22, 2018
-
-
Gabriel Mazetto authored
-
- Apr 12, 2018
-
-
Richard Clamp authored
These are only used during the multiple `bundle install` invocations; we don't need them in the final package.
-