-
Notifications
You must be signed in to change notification settings - Fork 283
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
[Bug]: Cannot release opensearch-ruby 3.2.0 because of Jenkins #4624
[Bug]: Cannot release opensearch-ruby 3.2.0 because of Jenkins #4624
Comments
The docker image used in the release: opensearchstaging/ci-runner:release-centos7-clients-v4 (see code) I tried pulling the image and looking at the installed ruby versions.
Looks like these are only versions installed on the docker file: https://github.com/opensearch-project/opensearch-build/blob/main/docker/ci/dockerfiles/current/release.centos7.clients.x64.arm64.dockerfile#L138-L141 @peterzhuamazon I believe for additional versions we either need to update the image or have something generic that would install it on the go? |
That seems to be the way to go, yes. Can you try running So there needs to be made a change at https://github.com/opensearch-project/opensearch-build-libraries/blob/6d35e942e98e1acddd88633a2aa1bbe39ab5e002/vars/publishToRubyGems.groovy#L27 as well. Do these things actually run as root? My first instict is that they would run as whatever https://build.ci.opensearch.org/blue/organizations/jenkins/opensearch-ruby-gems-release/detail/opensearch-ruby-gems-release/29/pipeline/ which was run before that commit about changing the user doesn't show the rvm error. I've openend opensearch-project/opensearch-build-libraries#410 So, two issues. A more recent ruby version needs to be added to the image anyways. |
This is what I see when I use above command:
Note that I am logged in as What version of ruby would need to be installed? |
The release action currently uses The latest patch release at this time is |
I would need to update the ruby from 2.6.0 to 3.0.2+, need to check the rvm support and rebuild images with changes. |
Send PR soon. |
Able to build:
|
Hi @nhtruong please confirm if ruby version 3.1.2 is good for you. Thanks. |
The above PR merged and will have the image available in 5 hours or so due to the complexity of this image. We can try to release next week. Thanks. |
The opensearch-ruby workflow need to switch to 3.1.2 ruby before run the build. Thanks. |
That sound good, thank you for your work. Is opensearch-project/opensearch-build-libraries#410 not an issue for the release? |
I have openend PR opensearch-project/opensearch-build-libraries#413 for the above issue. |
Attempted to redo the release but still failed. With different errors this time: https://build.ci.opensearch.org/blue/organizations/jenkins/opensearch-ruby-gems-release/detail/opensearch-ruby-gems-release/33/pipeline |
Hi @nhtruong |
We got past the previous error but got another one: https://build.ci.opensearch.org/blue/organizations/jenkins/opensearch-ruby-gems-release/detail/opensearch-ruby-gems-release/34/pipeline
|
Maybe the |
I think you are right @Earlopain
Will check if exact steps in the code to see if that is the issue. |
And our theory is right. Ruby version needs to be switched before the cert is added. Did not think that would make a difference
Will create a PR to fix this. |
Closing it as the issue is resolved now! |
Describe the bug
The release of Ruby 3.2.0 was first triggered in Feb 2024 and failed with the following error:
We tried to upgrade the rubyVersion of Jenkins to 3.0.6 but Jenkins still failed with the exact error.
We notice in the error message that RVM could not pick up the correct Ruby version:
To reproduce
Build and install the gem with Ruby 2.6
opensearch-project/opensearch-ruby#238 (comment)
Additional context
Check out the discussion on the Ruby client repo.
The text was updated successfully, but these errors were encountered: