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

"Helper is null, unable to run trigger" #118

Closed
ixdy opened this issue Jun 20, 2015 · 2 comments
Closed

"Helper is null, unable to run trigger" #118

ixdy opened this issue Jun 20, 2015 · 2 comments

Comments

@ixdy
Copy link
Contributor

ixdy commented Jun 20, 2015

The Jenkins log constantly shows severe-level error messages of the form

Jun 19, 2015 5:12:01 PM SEVERE org.jenkinsci.plugins.ghprb.GhprbTrigger run
Helper is null, unable to run trigger

It's unclear whether these messages are benign or indicative of a problem. If they are a configuration issue, they give no hint at to what is actually wrong or how one could fix the issue.

@DavidTanner
Copy link
Contributor

I have seen that also, let me see what I might be able to do

@DavidTanner
Copy link
Contributor

I am guessing you have a project that is disabled, but has the trigger set up in the configuration. The problem arises when you restart jenkins, the plugin will start and run even though the plugin is disabled. Usually the project reference is only kept by the helper, so checking to see if the project is disabled wouldn't work if the helper is null.

I am adding a reference to the project in the Trigger class, and see if we can get rid of this nuisance.

nosmo pushed a commit to nosmo/ghprb-plugin that referenced this issue Dec 12, 2018
Remove a null pointer error, fixes #jenkinsci#117
Cleanup some of the logging in the main trigger, fixes jenkinsci#118
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants