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

Null pointer exception GitlabMergeRequestWrapper.java:89 #100

Open
clgalassi opened this issue Dec 5, 2014 · 4 comments
Open

Null pointer exception GitlabMergeRequestWrapper.java:89 #100

clgalassi opened this issue Dec 5, 2014 · 4 comments

Comments

@clgalassi
Copy link

Hi,

We can not run this plugin for more than one instance project at our server. At crontab the log informs:

Dec 04, 2014 2:55:04 PM hudson.triggers.Trigger checkTriggers
WARNING: org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run() failed for hudson.maven.MavenModuleSet@4f44ea0b[adv-merge-validation]
java.lang.NullPointerException
at org.jenkinsci.plugins.gitlab.GitlabMergeRequestWrapper.check(GitlabMergeRequestWrapper.java:89)
at org.jenkinsci.plugins.gitlab.GitlabRepository.check(GitlabRepository.java:83)
at org.jenkinsci.plugins.gitlab.GitlabRepository.check(GitlabRepository.java:65)
at org.jenkinsci.plugins.gitlab.GitlabMergeRequestBuilder.run(GitlabMergeRequestBuilder.java:27)
at org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run(GitlabBuildTrigger.java:100)
at hudson.triggers.Trigger.checkTriggers(Trigger.java:266)
at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)

Is this a bug? Please, what we could do to fix it?

Thanks in advance
Carlos Galassi

@pwojda
Copy link

pwojda commented Dec 9, 2014

I got exact the same problem when there was a merge request that had it's branch deleted already (manual merge and not closed merge request at gitlab).
I think merge requests that for whatever reason doesn't contain any commits should be skipped by the plugin.

@pwojda
Copy link

pwojda commented Dec 9, 2014

I've noticed that current version skips MRs without commits, next release should fix it.

@fehmicansaglam
Copy link

I am also having the same problem. Can it be a configuration issue?

@baskaran-md
Copy link

What is the version of GitLabs and the Jenkins Plugin for GitLabs-merge-request-builder?

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

4 participants