|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Kenneth Baltrinic: To clarify, the 'Groovy script' build step is not affected (unsurprising, as it's a straightforward groovy invocation), but the 'system Groovy script' build step in Groovy plugin is?
Regarding scope, did you contact the reporter or is that your interpretation of this report? (Note that not too long ago, component names did not have the '-plugin' suffix making it difficult to tell in some cases whether a report is about the "something" related features in Jenkins, or the "something plugin".)
I'm asking because I'd like to split this into one issue per component. This way (IMO) the issues have a change to actually get implemented by the respective plugins'/core maintainers.