[JIRA] (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
Title: Message Title Daniel Spilker resolved as Fixed 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. Jenkins / 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 Change By: Daniel Spilker Status: Open Resolved Assignee: R. Tyler Croy Daniel Spilker Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (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
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38145 Re: The "buildWrappers" section of config.xml is not loaded upon reloading config from disk when the Pyenv and Ruby Runtime Plugins are enabled 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 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (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
Title: Message Title Dave Hildebrandt commented on JENKINS-38145 Re: The "buildWrappers" section of config.xml is not loaded upon reloading config from disk when the Pyenv and Ruby Runtime Plugins are enabled updated to Major because it affects multiple plugins, appears to be core, and I have found 2 other filings of this bug. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (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
Title: Message Title Dave Hildebrandt commented on JENKINS-38145 Re: The "buildWrappers" section of config.xml is not loaded upon reloading config from disk when the Pyenv and Ruby Runtime Plugins are enabled seen also with rvm, timestamper, console log colorer and environment dashboard. All these plugins deposit parameters in the section of config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (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
Title: Message Title Dave Hildebrandt updated an issue Jenkins / 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 Change By: Dave Hildebrandt Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (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
Title: Message Title Dave Hildebrandt updated an issue Jenkins / 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 duplicate: https://issues.jenkins-ci.org/browse/JENKINS-37771 Change By: Dave Hildebrandt Component/s: core Component/s: rvm-plugin Component/s: timestamper-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (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
Title: Message Title Daniel Wright created an issue Jenkins / 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 Issue Type: Bug Assignee: R. Tyler Croy Components: pyenv-plugin, ruby-runtime-plugin Created: 2016/Sep/12 4:07 PM Environment: Jenkins 2.22 Ruby Runtime Plugin 0.13 Pyenv Plugin 0.07 Priority: Minor Reporter: Daniel Wright 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: "Jenkins::Tasks::BuildWrapperProxy" pluginid="pyenv"> "pyenv" ruby-class="String">pyenv "PyenvWrapper" pluginid="pyenv"> "pyenv" ruby-class="String">$HOME/.pyenv "pyenv" ruby-class="String">numpy,matplotlib,pytest,psutil,six,paramiko,pylint,pep8 "pyenv"
