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

The "buildWrappers" section of config.xml is not loaded upon reloading config from disk when the Pyenv and Ruby Runtime Plugins are enabled

XMLWordPrintable

      If the the "buildWrappers" section of a job's config.xml (corresponding to the "Build Environment" configuration section) contains a Pyenv Plugin configuration (see snippet below), the entire "buildWrappers" section will not be loaded in the Jenkins web interface (also any configuration that may be present for other plugins). It is not visible in the job's configuration page and is ignored when the job is built.

      The configuration file is not changed upon reload/restart. Of course, if the job's configuration is opened via the UI and then saved, it gets deleted (since the UI's Build Environment section is not populated as it was previously configured in the file).

      I can not reproduce the issue with Ruby Runtime Plugin version 0.12.

      The issue is triggered when the job's config.xml contains the following Pyenv Plugin configuration:

        <buildWrappers>
    <ruby-proxy-object>
      <ruby-object ruby-class="Jenkins::Tasks::BuildWrapperProxy" pluginid="pyenv">
        <pluginid pluginid="pyenv" ruby-class="String">pyenv</pluginid>
        <object ruby-class="PyenvWrapper" pluginid="pyenv">
          <pyenv__root pluginid="pyenv" ruby-class="String">$HOME/.pyenv</pyenv__root>
          <pip__list pluginid="pyenv" ruby-class="String">numpy,matplotlib,pytest,psutil,six,paramiko,pylint,pep8</pip__list>
          <pyenv__revision pluginid="pyenv" ruby-class="String">master</pyenv__revision>
          <version pluginid="pyenv" ruby-class="String">2.7.11</version>
          <ignore__local__version ruby-class="FalseClass" pluginid="pyenv"/>
          <pyenv__repository pluginid="pyenv" ruby-class="String">https://github.com/yyuu/pyenv.git</pyenv__repository>
        </object>
      </ruby-object>
    </ruby-proxy-object>
    <!-- some other Build Environment config. -->
</buildWrappers>

          [JENKINS-38145] The "buildWrappers" section of config.xml is not loaded upon reloading config from disk when the Pyenv and Ruby Runtime Plugins are enabled

          Dave Hildebrandt added a comment -

          duplicate: https://issues.jenkins-ci.org/browse/JENKINS-37771

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

          Dave Hildebrandt added a comment -

          seen also with rvm, timestamper, console log colorer and environment dashboard. All these plugins deposit parameters in the <buildWrappers> section of config.xml

          Dave Hildebrandt added a comment - seen also with rvm, timestamper, console log colorer and environment dashboard. All these plugins deposit parameters in the <buildWrappers> section of config.xml

          Dave Hildebrandt added a comment -

          updated to Major because it affects multiple plugins, appears to be core, and I have found 2 other filings of this bug.

          Dave Hildebrandt added a comment - updated to Major because it affects multiple plugins, appears to be core, and I have found 2 other filings of this bug.

          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

          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

          Daniel Spilker added a comment -

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

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

            daspilker Daniel Spilker
            danieldwright Daniel Wright
            Votes:
            4 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: