Skip to content

RUBY-3275 backport CI changes to 2.18 #2727

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

Merged
merged 20 commits into from
Jul 3, 2023

Conversation

jamis
Copy link
Contributor

@jamis jamis commented Jun 8, 2023

Backports the "update build hosts" and other CI changes to 2.18-stable.

Note: the serverless specs are failing on this branch now; this has been captured for further investigation in RUBY-3280.

jamis and others added 3 commits June 8, 2023 10:23
* Bump to latest toolchain and clean up specs to use consistent (and modern) build hosts

* fix config validation errors

* don't try to run ruby 2.7 on ubuntu2204

* bump submodule to get updated toolchain version

* rhel84 -> rhel80

* keep tweaking

* add "require_solo" helper

* for testing: pointing spec/shared at my own branch

* update spec/shared again to fix typo

* bump spec/shared version again to prevent apt-get install from prompting

* make sure cmake is installed for FLE runs

* don't test on 3.2 yet (broken tests)

* make sure we check for cmake BEFORE the bundle is installed

* use MDB 5.x for testing certain auth mechanisms

this is because run-tests.sh uses `mongo` to configure the MDB instance for
certain auth mechanisms, which isn't shipped in MDB 6+.

* try building the native extension for mongo_kerberos

* remove jruby-9.4 for now to see if things pass any better with 9.3

* bump spec/shared to get updated server registry (for aarch64 versions)

* update serverless to use rhel80

* move the install_cmake function to spec/shared, and make sure it gets called in run-tests-gcp

* don't run zstd tests on jruby (no support)

* bump spec/shared to get updated target arch selection

* replace jruby 9.4 with 9.3 in sample_rubies list

* bump spec/shared again

* make sure kerberos stuff doesn't get confused by the BUNDLE_GEMFILE variable

* don't test jruby on arm for now

* don't assume x86_64 architecture

* fix invalid config

* jruby-9.3 isn't being built for ubuntu/debian :/

* need to build the bundle for the kerberos gem before compiling it

* bump spec/shared to latest from my branch

* jruby-9.3 is being built as a recent ruby now

* don't include ruby-3.2 in supported rubies (yet)

* rebuild config.yml

* bump spec/shared

* leaving out debian11 for now; we have ubuntu2204, which is closely related

* the file is /etc/os-release, not /etc/os_release

* remove jruby from FLE tests

* comment out the failing tests (and reference the corresponding Jira tickets)

this will at least let us get this "build hosts" effort sorted

* forgot to comment out 'latest'

* cmake is only needed if the helper is being installed

Co-authored-by: Dmitry Rybakov <dmitry.rybakov@mongodb.com>

* bump spec/shared

---------

Co-authored-by: Dmitry Rybakov <dmitry.rybakov@mongodb.com>
@jamis jamis changed the title RUBY-3275 backport to 2.18 RUBY-3275 backport CI changes to 2.18 Jun 8, 2023
comandeo-mongo and others added 12 commits June 13, 2023 10:48
* RUBY-3275 Update Atlas certificate

* Add a custom error message
all this to fix a ruby 3.2 incompatibility
…alidating_keys (mongodb#2620)

* RUBY-3117 investigate and fix test failures as a result of removing validating_keys

* RUBY-3117 remove all references to BSON::Config.validating_keys?

* Update gemfiles/bson_master.gemfile

Co-authored-by: Oleg Pudeyev <39304720+p-mongo@users.noreply.github.com>

Co-authored-by: Oleg Pudeyev <39304720+p-mongo@users.noreply.github.com>
@jamis jamis requested a review from comandeo June 21, 2023 17:14
@jamis jamis merged commit 3c11a2f into mongodb:2.18-stable Jul 3, 2023
@jamis jamis deleted the 3232-backport-to-2.18 branch July 3, 2023 16:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants