[JIRA] (JENKINS-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Jesse Glick commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts It took me a while to understand what is being discussed here. In summary: a custom Groovy script sets an unserializable value to some Jenkins global configuration; and thereafter every attempt to save that top-level settings object (e.g., a GlobalConfiguration) reports an error. Indeed restarting Jenkins would correct the situation (because it would load from the last version of the settings that were correctly serialized); you could also fix this without a restart simply by setting a valid object. I do not think there is anything else to say here—using system Groovy scripts is tantamount to writing a custom plugin, and no particular level of safety is guaranteed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts I have noticed that in this specific scenario, resaving the ToolProperty through the UI (by resaving the node from the UI for example) fixes the "in-memory" issue. Oleg Nenashev I understand this is not a defect, that Jenkins correctly rejects the proxy class. But maybe we could create a bug about the fact that it corrupts the groovy "in-memory" model, what's you opinion on that matter ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Allan BURDAJEWICZ yes, it can be technically prevented in this case. Not by Script Security, but by another engine Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Oleg Nenashev And that could be caused by any groovy class being rejected by the ClassFilter ? I mean that any user that trigger that kind of rejection via a groovy script could potentially impact the entire instance ? I wonder if that could be prevented / detected with script security (whether I would see the groovyProxy type in the signature to approve) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Allan BURDAJEWICZ > Or does it also impact instantiation through traditional API (creating a node with the tool property from the UI) ? It should not. Keep in mind that Groovy script invocation impacts the in-memory model, and most likely you will not be able to reconfigure the tool properties from Web UI until the bogus property gets removed by restart or a manual edit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts > You will also need to restart the Jenkins instance to cleanup memory model from non-serializable objects Hi Oleg Nenashev could you elaborate on this ? In that example the instantiation of ToolLocationNodeProperty.ToolLocation is broken until we restart, but is it only impacting instantiation via Groovy script ? Or does it also impact instantiation through traditional API (creating a node with the tool property from the UI) ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50743 ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Change By: Oleg Nenashev Labels: JEP-200 JEP-200-rejected groovy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev resolved as Not A Defect Jenkins / JENKINS-50743 ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50743 ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Change By: Oleg Nenashev Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev commented on JENKINS-50743 Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts So, "toolLocation as List" creates a Groovy proxy class. If you replace it by "[toolLocation]", the script will work well. You will also need to restart the Jenkins instance to cleanup memory model from non-serializable objects. I consider it as not a defect, Jenkins behaves correctly by rejecting the proxy class Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title
Oleg Nenashev commented on JENKINS-50743
Re: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
My repro script:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
import hudson.tools.*;
import hudson.slaves.*;
def dumb = Jenkins.instance.getComputer("dumb").node
def gitToolDescriptor = Jenkins.getInstance().getDescriptor("hudson.plugins.git.GitTool")
def toolLocation = new ToolLocationNodeProperty.ToolLocation(gitToolDescriptor, "foo", "bar")
def toolLocationProperty = new ToolLocationNodeProperty(toolLocation as List)
def evnp = new EnvironmentVariablesNodeProperty()
dumb.nodeProperties.add(evnp)
dumb.nodeProperties.add(toolLocationProperty)
Jenkins.instance.addNode(dumb)
createdNodes.add(slaveName)
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
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.
[JIRA] (JENKINS-50743) ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50743 ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Change By: Oleg Nenashev Summary: ToolLocationNodeProperty - JEP-200 issue when configuring tools from Groovy scripts Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
