Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56211

RVM plugin is broken on Java 11

    XMLWordPrintable

Details

    Description

      The plugin test was failing in a while as it depends on either presence of the software installed in the ci.jenkins.io nodes or an ability to install it while none of it is available there. The test should be rewritten (either in ATH or the plugin sources itself) using docker-fixtures (for example) to verify both scenarios (tools installed already, tools to be installed).

      jglick, eitoball, are you interested in saving the test?

      [1] https://github.com/jenkinsci/acceptance-test-harness/blob/7e8c9b20d25e420c37940313f8243e21c86be1bb/src/test/java/plugins/RvmPluginTest.java

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-48116 Jenkins 2.91 breaks builds which require Ruby

          • Major - Major loss of function.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            jglick Jesse Glick added a comment -

            I am not interested. danielbeck drafted JEP-7 which would make it deprecated. The plugin has not had a release in three years. The test was introduced to verify the core workaround for JENKINS-48116; the plugin side of the fix is to my knowledge still unreleased, hence JEP-7.

            jglick Jesse Glick added a comment - I am not interested. danielbeck drafted JEP-7 which would make it deprecated. The plugin has not had a release in three years. The test was introduced to verify the core workaround for JENKINS-48116 ; the plugin side of the fix is to my knowledge still unreleased, hence JEP-7.
            danielbeck Daniel Beck added a comment -

            FWIW I think oleg_nenashev recently pointed out that ruby-runtime does not work with Java 11 anyway?

            danielbeck Daniel Beck added a comment - FWIW I think oleg_nenashev recently pointed out that ruby-runtime does not work with Java 11 anyway?
            jglick Jesse Glick added a comment -

            Huh. danielbeck do you intend to push JEP-7 forward?

            jglick Jesse Glick added a comment - Huh. danielbeck do you intend to push JEP-7 forward?
            oleg_nenashev Oleg Nenashev added a comment -

            > FWIW I think oleg_nenashev recently pointed out that ruby-runtime does not work with Java 11 anyway?

             

            I do not remember that, sorry. I definitely see some architectural problems in the Ruby Runtime for Java 11, but I do not think we have ever tested it. There were issues around JAXB which would impact Ruby runtime, but it should be fixed now in 2.163+

             

             

            oleg_nenashev Oleg Nenashev added a comment - > FWIW I think oleg_nenashev recently pointed out that ruby-runtime does not work with Java 11 anyway?   I do not remember that, sorry. I definitely see some architectural problems in the Ruby Runtime for Java 11, but I do not think we have ever tested it. There were issues around JAXB which would impact Ruby runtime, but it should be fixed now in 2.163+    
            oleg_nenashev Oleg Nenashev added a comment - - edited

            Oliver: JRuby library might be a root cause

            oleg_nenashev Oleg Nenashev added a comment - - edited Oliver: JRuby library might be a root cause
            timja Tim Jacomb added a comment -

            closing as https://jenkins.io/jep/7 is progressing and there's no plans to touch any ruby-runtime based plugins again.

            timja Tim Jacomb added a comment - closing as https://jenkins.io/jep/7 is progressing and there's no plans to touch any ruby-runtime based plugins again.

            People

              Unassigned Unassigned
              olivergondza Oliver Gondža
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: