You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our CI builds started failing at the bundle step because there stopped being an openssl link when bundling. We tried to manually install openssl before installing ruby eg sudo apt-get update && sudo apt-get install -y openssl which installs the latest openssl version 3.
When rvm was installed via the ruby/install step, we noticed theres a check in the orb that looks for an existing ssl version to use in the opts flags, but it only looks for versions within the 1 range. eg if ! openssl version | grep -q -E '1\\.[0-9]+\\.[0-9]+'. If the version is outside of that regex, it installs openssl 1.0.1 by default. This version (less than 1.1.1) causes issues with ssl certs when using sidekiq-pro (and assuming other gems) and prevents bundling from happening
Expected behavior:
I would hope the system would use any openssl version that was already installed on the machine, or at least default to using the latest 1 version instead of the oldest.
The text was updated successfully, but these errors were encountered:
Orb version: 2.1.0
What happened:
Our CI builds started failing at the bundle step because there stopped being an openssl link when bundling. We tried to manually install openssl before installing ruby eg
sudo apt-get update && sudo apt-get install -y openssl
which installs the latest openssl version 3.When rvm was installed via the ruby/install step, we noticed theres a check in the orb that looks for an existing ssl version to use in the opts flags, but it only looks for versions within the 1 range. eg
if ! openssl version | grep -q -E '1\\.[0-9]+\\.[0-9]+'
. If the version is outside of that regex, it installs openssl 1.0.1 by default. This version (less than 1.1.1) causes issues with ssl certs when using sidekiq-pro (and assuming other gems) and prevents bundling from happeningExpected behavior:
I would hope the system would use any openssl version that was already installed on the machine, or at least default to using the latest 1 version instead of the oldest.
The text was updated successfully, but these errors were encountered: