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

RVM configurations disabled when Jenkins restarts.

      All my rvm configurations is lost when jenkins restarts. They where all unchecked.

          [JENKINS-37353] RVM configurations disabled when Jenkins restarts.

          Same here!

          Benjamin Beermann added a comment - Same here!

          Updated jenkins and all my plugins. All my RVM configurations were wiped again...

          Jeremy Venezia added a comment - Updated jenkins and all my plugins. All my RVM configurations were wiped again...

          It happens when jenkins is restarted.

          Jeremy Venezia added a comment - It happens when jenkins is restarted.

          It is happening with the entire buildWrappers tag:

          config.xml.diff
          -  <buildWrappers>
          -    <hudson.plugins.timestamper.TimestamperBuildWrapper plugin="timestamper@1.8.7"/>
          -    <hudson.plugins.ansicolor.AnsiColorBuildWrapper plugin="ansicolor@0.4.3">
          -      <colorMapName>xterm</colorMapName>
          -    </hudson.plugins.ansicolor.AnsiColorBuildWrapper>
          -    <org.jenkinsci.plugins.environmentdashboard.DashboardBuilder plugin="environment-dashboard@1.1.4">
          -      <nameOfEnv>$environment</nameOfEnv>
          -      <componentName>deployment</componentName>
          -      <buildNumber>$BUILD_NUMBER</buildNumber>
          -      <buildJob></buildJob>
          -      <packageName></packageName>
          -      <data/>
          -      <addColumns>false</addColumns>
          -    </org.jenkinsci.plugins.environmentdashboard.DashboardBuilder>
          -    <ruby-proxy-object>
          -      <ruby-object ruby-class="Jenkins::Tasks::BuildWrapperProxy" pluginid="rvm">
          -        <pluginid pluginid="rvm" ruby-class="String">rvm</pluginid>
          -        <object ruby-class="RvmWrapper" pluginid="rvm">
          -          <impl pluginid="rvm" ruby-class="String">.</impl>
          -        </object>
          -      </ruby-object>
          -    </ruby-proxy-object>
          -  </buildWrappers>
          +  <buildWrappers/>
          

          Dave Hildebrandt added a comment - It is happening with the entire buildWrappers tag: config.xml.diff - <buildWrappers> - <hudson.plugins.timestamper.TimestamperBuildWrapper plugin= "timestamper@1.8.7" /> - <hudson.plugins.ansicolor.AnsiColorBuildWrapper plugin= "ansicolor@0.4.3" > - <colorMapName>xterm</colorMapName> - </hudson.plugins.ansicolor.AnsiColorBuildWrapper> - <org.jenkinsci.plugins.environmentdashboard.DashboardBuilder plugin= "environment-dashboard@1.1.4" > - <nameOfEnv>$environment</nameOfEnv> - <componentName>deployment</componentName> - <buildNumber>$BUILD_NUMBER</buildNumber> - <buildJob></buildJob> - <packageName></packageName> - <data/> - <addColumns> false </addColumns> - </org.jenkinsci.plugins.environmentdashboard.DashboardBuilder> - <ruby-proxy-object> - <ruby-object ruby-class= "Jenkins::Tasks::BuildWrapperProxy" pluginid= "rvm" > - <pluginid pluginid= "rvm" ruby-class= " String " >rvm</pluginid> - <object ruby-class= "RvmWrapper" pluginid= "rvm" > - <impl pluginid= "rvm" ruby-class= " String " >.</impl> - </object> - </ruby-object> - </ruby-proxy-object> - </buildWrappers> + <buildWrappers/>

          Dave Hildebrandt added a comment - related: https://issues.jenkins-ci.org/browse/JENKINS-37771

          Core issue appears to be that <buildWrappers> section of config.xml is not restored on restart. Workaround is to manuallty fix each job that uses that mechanism.

          Dave Hildebrandt added a comment - Core issue appears to be that <buildWrappers> section of config.xml is not restored on restart. Workaround is to manuallty fix each job that uses that mechanism.

          eitoball can you take a look? ruby-runtime 0.13 seems to cause problems.

          Daniel Spilker added a comment - eitoball can you take a look? ruby-runtime 0.13 seems to cause problems.

          Code changed in jenkins
          User: Daniel Spilker
          Path:
          src/main/resources/artifact-ignores.properties
          http://jenkins-ci.org/commit/backend-update-center2/803812c3149e03194f3e77a39c1dcd7a1c27eca7
          Log:
          do not distribute ruby-runtime 0.13 (#101)

          see JENKINS-37353, JENKINS-37771 and JENKINS-38145

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Daniel Spilker Path: src/main/resources/artifact-ignores.properties http://jenkins-ci.org/commit/backend-update-center2/803812c3149e03194f3e77a39c1dcd7a1c27eca7 Log: do not distribute ruby-runtime 0.13 (#101) see JENKINS-37353 , JENKINS-37771 and JENKINS-38145

          ruby-runtime 0.13 is no longer available in the Update Center

          Daniel Spilker added a comment - ruby-runtime 0.13 is no longer available in the Update Center

          Karl Brown added a comment - - edited

          Note: I'm still seeing this behavior, after having updated from Jenkins 2.2 to Jenkins 2.60.3.

          I am using ruby-runtime 0.12, but the behavior still occurs - on boot, the buildWrappers sections of any older jobs is deleted - removing RVM, but also ANSI-color plugins, and others.

          Any ideas on how to fix this?

          If I create a new job, it seems to be created correctly... I am looking for a work-around that doesn't involve updating all of my jobs by hand.

           

          Edit: I found this, in the readme:

          https://github.com/jenkinsci/rvm-plugin

          We were using a very old version of RVM plug-in, and need to execute these update instructions before upgrading to the new plugin version.

          Karl Brown added a comment - - edited Note: I'm still seeing this behavior, after having updated from Jenkins 2.2 to Jenkins 2.60.3. I am using ruby-runtime 0.12, but the behavior still occurs - on boot, the buildWrappers sections of any older jobs is deleted - removing RVM, but also ANSI-color plugins, and others. Any ideas on how to fix this? If I create a new job, it seems to be created correctly... I am looking for a work-around that doesn't involve updating all of my jobs by hand.   Edit: I found this, in the readme: https://github.com/jenkinsci/rvm-plugin We were using a very old version of RVM plug-in, and need to execute these update instructions before upgrading to the new plugin version.

            daspilker Daniel Spilker
            jvenezia Jeremy Venezia
            Votes:
            8 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: