The DSL keyword implementation is just a dozen lines, so easy to re-implement and extend.
As I said, I'm giving up with this plugin, so if someone volunteer and want to resurrect workspace support, all yours 2014-05-02 14:55 GMT+02:00 Les Mikesell <[email protected]>: > On Fri, May 2, 2014 at 7:07 AM, nicolas de loof > <[email protected]> wrote: > > groovy DSL was only a quick and dirty implementation, I planned to have > > something more robust (and resumable), but with people to use it as a > > development console I don't have any option to change internal design > now. > > This plugin was considered experimental, and I won't invest much time on > it > > as I consider it's design broken. > > > > Would there be a way to refactor your groovy classes into something > that could be used as a library by a generic groovy job where being > able to do other useful operations would not be considered a bug? It > would be nice to be able to run other jobs in parallel with some error > checking without needing to understand the full jenkins api or being > a groovy expert but without being intentionally restricted. > > -- > Les Mikesell > [email protected] > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" 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. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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.
