Thanks
J
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/o
The repo has been forked:
https://github.com/jenkinsci/matrix-groovy-execution-strategy-plugin
четверг, 23 октября 2014 г., 12:44:10 UTC+4 пользователь Jeremy Marshall
написал:
>
> I think the plugin can be forked, but it's better to agree on the plugin
>>> name before forking.
>>>
>>
>
>
> I think the plugin can be forked, but it's better to agree on the plugin
>> name before forking.
>>
>
I renamed the plugin to
https://github.com/JeremyMarshall/matrix-groovy-execution-strategy-plugin
>
>>- What about using http://groovy-sandbox.kohsuke.org/ to run Groovy
>>
I think the plugin can be forked, but it's better to agree on the plugin
name before forking.
- What about using http://groovy-sandbox.kohsuke.org/ to run Groovy
scripts? Just to avoid new security holes...
- > "I think the name could be better "
- Definitely. Actually, you don't
Hi
I put together a matrix execution strategy which allows greater control
than the default strategy.
It will run either a groovy script, as entered or a script from an absolute
path or from the workspace.
This is probably best suited to dynamically built axis.
There are a couple of problems
