|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
@Arthur - I also have this problem, but I don't have the lines you mentioned in the last build's build.xml.
I found that manually triggering the build will release the scripttrigger error until the next time I restart or reload Jenkins.
BTW - my environment is Jenkins 1.510 with ScriptTrigger 0.22, running on a windows server 2008 (trigger on a CentOS 6 slave) and another instance running on a windows server 2003 (trigger on master).