Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiplying triggers #304

Closed
lemmuu opened this issue Apr 3, 2024 · 1 comment
Closed

Multiplying triggers #304

lemmuu opened this issue Apr 3, 2024 · 1 comment
Labels

Comments

@lemmuu
Copy link

lemmuu commented Apr 3, 2024

Jenkins and plugins versions report

Hello,
Yesterday I update the plugins in Jenkins (currently on 2.440.2) in bulk, amongst them, updating Generic Webhook Trigger to latest (2.1.0) and suddenly I have multiplied triggers for one webhook.

Webhook server log was telling me error code 500, with 5 retries, although the build was triggered indeed 5 times for each POST call.

I am seeing in the Jenkins log messages like:
[id=6297] SEVERE o.j.p.g.GenericWebHookRequestReceiver#doInvoke: SecondaryDataMerge
java.lang.NullPointerException: Cannot invoke "hudson.model.Queue$Item.getUrl()" because "item" is null
at org.jenkinsci.plugins.gwt.GenericTrigger.trigger(GenericTrigger.java:230)
at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:192)
at org.jenkinsci.plugins.gwt.GenericWebHookRequestReceiver.doInvoke(GenericWebHookRequestReceiver.java:98)
...

Also, this was only happening for a few builds, all triggered through the same tunnel, but everything, the jobs, the tunnel is configured in the exact same was as other ones. The only difference between ones that had the issue and ones that didn't was the source of the hook, coming from different Plastic SCM repos.

Rolling back to version 2.0.0 fixes the issue

Pipeline script and build log I think are irrelevant since this issue was happening before running the Pipeline, at the trigger step.

@tomasbjerre
Copy link
Contributor

Thanks for reporting. Releasing a fix now in 2.1.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants