Getting null pointer exception on comment #23
Labels
Comments
|
Does it happen with every MR? Or just with one of them?
Den tis 8 okt. 2019 10:38Arbuzov Sergey <[email protected]> skrev:
… Plugin version 2.31
Jenkins version 2.138.3
Pipeline command
`
step([
$class: 'ViolationsToGitLabRecorder',
config: [
gitLabUrl: 'https://mygitlabserver/',
projectId: 'projectgroup/project-name',
mergeRequestIid: env.gitlabMergeRequestIid,
//createCommentWithAllSingleFileComments: true,
createSingleFileComments: true,
//commentOnlyChangedContent: true,
commentOnlyChangedFiles: true,
minSeverity: 'INFO',
maxNumberOfViolations: 99999,
enableLogging: true,
apiTokenCredentialsId: 'jenkins-violations-secret',
apiTokenPrivate: true,
authMethodHeader: true,
ignoreCertificateErrors: true,
keepOldComments: false,
commentTemplate: """___
*Reporter*: {{violation.reporter}}{{#violation.rule}}
*Rule*: {{violation.rule}}{{/violation.rule}}
*Severity*: {{violation.severity}}
*File*: {{violation.file}} L{{violation.startLine}}{{#violation.source}}
*Source*: {{violation.source}}{{/violation.source}}
{{violation.message}}
""",
violationConfigs: [
[ pattern: '.*checkstyle\.xml$', parser: 'CHECKSTYLE', reporter:
'Checkstyle' ]
]
]
])
`
java.lang.NullPointerException at
se.bjurr.violations.comments.gitlab.lib.GitLabCommentsProvider.createSingleFileComment(GitLabCommentsProvider.java:161)
at
se.bjurr.violations.comments.lib.CommentsCreator.createSingleFileComments(CommentsCreator.java:147)
at
se.bjurr.violations.comments.lib.CommentsCreator.createComments(CommentsCreator.java:71)
at
se.bjurr.violations.comments.lib.CommentsCreator.createComments(CommentsCreator.java:38)
at
se.bjurr.violations.comments.gitlab.lib.ViolationCommentsToGitLabApi.toPullRequest(ViolationCommentsToGitLabApi.java:175)
at
org.jenkinsci.plugins.jvctgl.perform.JvctglPerformer.doPerform(JvctglPerformer.java:160)
at
org.jenkinsci.plugins.jvctgl.perform.JvctglPerformer$2.invoke(JvctglPerformer.java:268)
at
org.jenkinsci.plugins.jvctgl.perform.JvctglPerformer$2.invoke(JvctglPerformer.java:256)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at
hudson.remoting.UserRequest.perform(UserRequest.java:212) at
hudson.remoting.UserRequest.perform(UserRequest.java:54) at
hudson.remoting.Request$2.run(Request.java:369) at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23?email_source=notifications&email_token=AADLKE5GWXYZIVRRDDIHPZDQNRBHLA5CNFSM4I6OVJIKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HQJAFTA>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AADLKE2GQYGCNOUH66HZGX3QNRBHLANCNFSM4I6OVJIA>
.
|
tomasbjerre
added a commit
that referenced
this issue
Oct 8, 2019
|
Releasing 2.32 that should give a clearer error, but still not solving the issue. |
|
It happens with every MR |
|
Did you try the new version? What is the new error? |
|
The current error seems to be the same (on version 2.32): |
|
No that is very different stacktrace. Now you are missing project and merge request iid: |
|
hmm shouldnt it use the global one by default? |
|
Sorry. |
|
What is the response of this? |
|
Please find attached all response in the archive |
tomasbjerre
added a commit
to tomasbjerre/violation-comments-to-gitlab-lib
that referenced
this issue
Oct 9, 2019
tomasbjerre
added a commit
that referenced
this issue
Oct 9, 2019
tomasbjerre
added a commit
that referenced
this issue
Oct 9, 2019
tomasbjerre
added a commit
that referenced
this issue
Oct 9, 2019
|
Released 2.34 now. Should fix the problem. Available in the update site within hours. |
|
I am afraid not yet. Full log in zip to avoid search indexing |
|
Strange, what is the response of this? |
|
See attached |
|
The problem is that In Gitlab.com it is there: It should also be there according to the docs: |
|
I tried Gitlab 10.7.3 and I can also see that |
|
Thanks a lot for the clarification. |
|
I updated my gitlab instance to 12.3.5 and the issue was fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Plugin version 2.31
Jenkins version 2.138.3
Gitlab 10.7.3 ce
Pipeline command
Stack trace during the build
The text was updated successfully, but these errors were encountered: