Closed Alyust closed 5 years ago
Yes, I agree that @nickgrealy did a great job :) Can you, please, explain why do you need this feature? Which User Scenario needs it?
p.s. I now that this feature can be implemented quite easy, but, unfortunately, current state of master blocks new releases (it breaks some feature that are really useful, i.e. ability to import any class from any plugin").
I mean a line edit by the 'Test Groovy Code' button in plugin configuration section. It's content ('RunListener.onStarted' by default) goes to 'event' variable for running 'Groovy Code'. The scenario is testing: now I have to additionally handle 'RunListener.onStarted' event in my script when in fact it is supposed to only handle 'GlobalEventsPlugin.start'. And things might get hairier when there will be a need to handle job start also, or handle 2+ events in different ways.
I see. I think this button should fire GlobalEventsPlugin.start
. Probably it was broken during some refactoring :)
Thank you guys for this cool plugin that let me not to write my own one! ;)
A tiny enhancement request: configurable test event instead of just 'RunListener.onStarted'