I have a strange behavior by my Jenkins and the ScriptTrigger<https://wiki.jenkins-ci.org/display/JENKINS/ScriptTrigger+Plugin> plugin.
I have Jenkins 1.510 with the latest version of this plugin. I have the trigger setup with a simple shell script: #!/bin/bash echo test exit 0 The trigger is set to start the build if exit code is 0. After I restart Jenkins (or just reload configuration), the trigger log shows: ... The expected script execution code is 0 [ERROR] - SEVERE - Polling error null No error is in any of the other logs I looked. No comes the puzzle - if I trigger the job manually, it will make the plugin for this job only start working properly until the next restart... Has anyone seen this? Does anyone have an idea? -- 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/groups/opt_out.
