|
||||||||
|
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.
You're right, the workflow-plugin is a complex piece of software, and it gets obvious in the test automation (kudos to Kohsuke Kawaguchi, and to you!). I now understand, that the test environment is tricky, and ironing out race-conditions isn't easy. If reporting such issues helps, please let me know.
However, I'd like to do some experiments with the code, and maybe the things I'd like to implement are out of my reach. In any case, I won't tamper with the CPS/Groovy magic at the heart of the plugin, and if I get anything of general interest, I'll use a pull-request for testing, like you suggested.
Thanks for all the useful hints, and thanks for pointing out JENKINS-18578 - it has an impact on one of my use cases for Jenkins, and I guess you just saved me days of work.