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

"Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Environment:
      1 jenkins server with multiple slaves
      all jobs affected by this are executed by the same slave.
      All the jobs that have been configured to use the plugin and use the "Run the build in a RVM-managed environment" option, after restarting the jenkins, lose this setting.
      The "Run the build in a RVM-managed environment" check box is unchecked after server restart.

      using RVM plugin 0.6

        Attachments

          Issue Links

            Activity

            Hide
            wallamatt Matthew Hessing added a comment -

            Our team is encountering the same issue. Our build machine is a mac mini running Jenkins 2.35. On each machine restart or jenkins restart, all Build Environment options are cleared. This includes Delete workspace, setting the Ruby environment using RVM or rbenv, and all Android emulator options. We have over a dozen jobs and are creating more daily; it is painful to go back and update these on each restart.

            Note: I rolled back to ruby-runtime 0.12 and did not see any improvements.

            Show
            wallamatt Matthew Hessing added a comment - Our team is encountering the same issue. Our build machine is a mac mini running Jenkins 2.35. On each machine restart or jenkins restart, all Build Environment options are cleared. This includes Delete workspace, setting the Ruby environment using RVM or rbenv, and all Android emulator options. We have over a dozen jobs and are creating more daily; it is painful to go back and update these on each restart. Note: I rolled back to ruby-runtime 0.12 and did not see any improvements.
            Show
            cantorman Dave Hildebrandt added a comment - related: https://issues.jenkins-ci.org/browse/JENKINS-37353
            Hide
            cantorman Dave Hildebrandt added a comment - - edited

            I have gone as far as to create an hourly job that commits changes to config.xml files in my jobs dir if they are updated. Later, jenkins crashed and the config.xml files were modified as noted earlier in this bug. I used git to revert the change and reloaded from config in two different ways:

            • I recovered the correct content using git with the server shut down, and when I started it up, the jobs did NOT have the config AND the config files had been modified to remove the correct settings.
            • I recovered the correct content using git with the server running, hit "reload config from disk" and after that completed, the jobs did NOT have the correct config. The config files were NOT modified in this case.
            Show
            cantorman Dave Hildebrandt added a comment - - edited I have gone as far as to create an hourly job that commits changes to config.xml files in my jobs dir if they are updated. Later, jenkins crashed and the config.xml files were modified as noted earlier in this bug. I used git to revert the change and reloaded from config in two different ways: I recovered the correct content using git with the server shut down, and when I started it up, the jobs did NOT have the config AND the config files had been modified to remove the correct settings. I recovered the correct content using git with the server running, hit "reload config from disk" and after that completed, the jobs did NOT have the correct config. The config files were NOT modified in this case.
            Hide
            scm_issue_link 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

            Show
            scm_issue_link 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
            Hide
            daspilker Daniel Spilker added a comment -

            ruby-runtime 0.13 is no longer available in the Update Center, you need to downgrade to 0.12 to fix the problem.

            Show
            daspilker Daniel Spilker added a comment - ruby-runtime 0.13 is no longer available in the Update Center, you need to downgrade to 0.12 to fix the problem.

              People

              • Assignee:
                daspilker Daniel Spilker
                Reporter:
                mvardi Menahem Vardi
              • Votes:
                12 Vote for this issue
                Watchers:
                21 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: