-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.22
Ruby Runtime Plugin 0.13
Pyenv Plugin 0.07
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>
- is duplicated by
-
JENKINS-37771 "Run the build in a RVM-managed environment" field gets unchecked after restarting the Jenkins server.
- Resolved
- is related to
-
JENKINS-39193 Unable to use rbenv plugin together with ruby environment plugin
- Closed