Jenkins ScriptTrigger plugin stopped working by default

[EldadAK]

I have a strange behavior by my Jenkins and the ScriptTrigger 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?

[Grégory Boissinot]

Please raise a new issue for the script-trigger component

--
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 jenkinsci-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Eldad A.K.]

Isn't it the same as: https://issues.jenkins-ci.org/browse/JENKINS-17566 ?

Eldad

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/v-pUMig3PCs/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.

[Grégory Boissinot]

I don't think so.

[EldadAK]

The problem was found to be related to the dependency to xtrigger lib version. I downloaded the sources, updated xtrigger.lib.version to be 0.19 and locally built the plugin (and installed it on my Jenkins). This solved the problem.

Thanks for the help of Gregory Boissinot (the author of the plugin), who helped me find this. He will release a formal release for this plugin soon.

Note - the current version is 0.22.