[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten closed an issue as Fixed Jenkins / JENKINS-60309 NPE when using with gitlab-plugin's statuses. Change By: ipleten Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.1974.1582075020346%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten assigned an issue to ipleten Jenkins / JENKINS-60309 NPE when using with gitlab-plugin's statuses. Change By: ipleten Assignee: Parichay Barpanda ipleten Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.3029.1581022260685%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten resolved as Fixed Fixed in https://github.com/jenkinsci/gitlab-plugin/pull/1014 https://github.com/jenkinsci/gitlab-plugin/pull/1012 Jenkins / JENKINS-60309 NPE when using with gitlab-plugin's statuses. Change By: ipleten Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To vie
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten commented on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. Should be fixed in gitlab-plugin-1.5.16 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.3019.1581022200231%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: "Null pointer exception" and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.Logs snapshot:{noformat} ov 27, 2019 6:59:00 PM io java . jenkins lang . plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener onCheckout NullPointerException INFO: SCMListener: Checkoutsoftware » pipe-test-build » MR-64-merge #5Nov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: Result: nullNov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: COMMIT: 2d46589fed77023cc5a4ac38422873408e5ce1cborg.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run") at org. gitlab4j eclipse . api jgit . AbstractApi lib . validate ObjectId.fromString ( AbstractApi ObjectId .java: 593 235 ) at org com . gitlab4j dabsquared . api gitlabjenkins . AbstractApi util . post CommitStatusUpdater.retrieveGitlabProjectIds ( AbstractApi CommitStatusUpdater .java: 264 195 ) at org com . gitlab4j dabsquared . api gitlabjenkins . CommitsApi util . addCommitStatus CommitStatusUpdater.updateCommitStatus ( CommitsApi CommitStatusUpdater .java: 452 61 ) at io com . jenkins dabsquared . plugins gitlabjenkins . gitlabbranchsource util . helpers CommitStatusUpdater . GitLabPipelineStatusNotifier.sendNotifications updateCommitStatus ( GitLabPipelineStatusNotifier CommitStatusUpdater .java: 249 97 ) at io com . jenkins dabsquared . plugins gitlabjenkins . gitlabbranchsource workflow . helpers.GitLabPipelineStatusNotifier.access GitLabBuildsStep $ 300 GitLabBuildStepExecution$1.onStart ( GitLabPipelineStatusNotifier GitLabBuildsStep .java: 51 85 ) at io org . jenkins jenkinsci .plugins. gitlabbranchsource workflow . helpers cps . GitLabPipelineStatusNotifier$JobCheckOutListener CpsBodyExecution . onCheckout launch ( GitLabPipelineStatusNotifier CpsBodyExecution .java: 373 135 ) at org.jenkinsci.plugins.workflow. steps cps . scm CpsBodyInvoker . SCMStep.checkout launch ( SCMStep CpsBodyInvoker .java: 140 187 ) at org.jenkinsci.plugins.workflow. libs cps . SCMSourceRetriever DSL$ThreadTaskImpl .lambda$ doRetrieve invokeBodiesAndSwitchToAsyncMode $ 1 0 ( SCMSourceRetriever DSL .java: 154 660 ) at org.jenkinsci.plugins.workflow. libs cps . SCMSo
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten edited a comment on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. I tried to fix the problem in gitlab-plugin:https://github.com/jenkinsci/gitlab-plugin/pull/1014https://github.com/jenkinsci/gitlab-plugin/pull/1012They haven't released that yet, but I checkout 1.5.13 (currently released as master breaks another things see: https://github.com/jenkinsci/gitlab-plugin/pull/916#issuecomment-57266272.) version and cherry-pick'ed both commits to branch and build self-hosted version.Give it a try. *UPDATE:* you right about log. I've updated summary with correct log. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.5761.1578592140808%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten edited a comment on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. I tried to fix the problem in gitlab-plugin:https://github.com/jenkinsci/gitlab-plugin/pull/1014https://github.com/jenkinsci/gitlab-plugin/pull/1012They haven't released that yet, but I checkout 1.5.13 (currently released as master breaks another things see: https://github . com/jenkinsci/gitlab-plugin/pull/916#issuecomment-57266272. ) version and cherry-pick'ed both commits to branch and build self-hosted version.Give it a try. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.5753.1578592020250%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten commented on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. I tried to fix the problem in gitlab-plugin: https://github.com/jenkinsci/gitlab-plugin/pull/1014 https://github.com/jenkinsci/gitlab-plugin/pull/1012 They haven't released that yet, but I checkout 1.5.13 (currently released as master breaks another things.) version and cherry-pick'ed both commits to branch and build self-hosted version. Give it a try. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.5751.1578591840204%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title Peter Leibiger commented on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. I am seeing the same stack without the nullpointer, only the second part. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.5387.1578529260202%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten updated an issue Jenkins / JENKINS-60309 NPE when using with gitlab-plugin's statuses. Change By: ipleten Component/s: gitlab-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.7909.1574886360223%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title ipleten commented on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. Looks like NPE goes from gitlan-plugin in https://github.com/jenkinsci/gitlab-plugin/blob/master/src/main/java/com/dabsquared/gitlabjenkins/util/CommitStatusUpdater.java#L185 It expect class to be an instance of "AbstractGitSCMSource.SCMRevisionImpl" but for MergeRequest it's a "ChangeRequestSCMRevision" in https://github.com/jenkinsci/gitlab-branch-source-plugin/blob/master/src/main/java/io/jenkins/plugins/gitlabbranchsource/MergeRequestSCMRevision.java#L8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203304.1574879165000.7907.1574886360198%40Atlassian.JIRA.
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: "Null pointer exception" and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.Logs snapshot:{noformat}ov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener onCheckoutINFO: SCMListener: Checkoutsoftserve Checkoutsoftware » pipe-test-build -ipleten » MR-64-merge #5Nov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: Result: nullNov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: COMMIT: 2d46589fed77023cc5a4ac38422873408e5ce1cborg.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run") at org.gitlab4j.api.AbstractApi.validate(AbstractApi.java:593) at org.gitlab4j.api.AbstractApi.post(AbstractApi.java:264) at org.gitlab4j.api.CommitsApi.addCommitStatus(CommitsApi.java:452) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.sendNotifications(GitLabPipelineStatusNotifier.java:249) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.access$300(GitLabPipelineStatusNotifier.java:51) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener.onCheckout(GitLabPipelineStatusNotifier.java:373) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:140) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.lambda$doRetrieve$1(SCMSourceRetriever.java:154) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrySCMOperation(SCMSourceRetriever.java:104) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:153) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:93) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(Co
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: "Null pointer exception" and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working. Logs snapshot:{noformat}ov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener onCheckoutINFO: SCMListener: Checkoutsoftserve » pipe-test-build-ipleten » MR-64-merge #5Nov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: Result: nullNov 27, 2019 6:59:00 PM io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier sendNotificationsINFO: COMMIT: 2d46589fed77023cc5a4ac38422873408e5ce1cborg.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run") at org.gitlab4j.api.AbstractApi.validate(AbstractApi.java:593) at org.gitlab4j.api.AbstractApi.post(AbstractApi.java:264) at org.gitlab4j.api.CommitsApi.addCommitStatus(CommitsApi.java:452) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.sendNotifications(GitLabPipelineStatusNotifier.java:249) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier.access$300(GitLabPipelineStatusNotifier.java:51) at io.jenkins.plugins.gitlabbranchsource.helpers.GitLabPipelineStatusNotifier$JobCheckOutListener.onCheckout(GitLabPipelineStatusNotifier.java:373) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:140) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.lambda$doRetrieve$1(SCMSourceRetriever.java:154) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrySCMOperation(SCMSourceRetriever.java:104) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.doRetrieve(SCMSourceRetriever.java:153) at org.jenkinsci.plugins.workflow.libs.SCMSourceRetriever.retrieve(SCMSourceRetriever.java:93) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.retrieve(LibraryAdder.java:157) at org.jenkinsci.plugins.workflow.libs.LibraryAdder.add(LibraryAdder.java:138) at org.jenkinsci.plugins.workflow.libs.LibraryDecorator$1.call(LibraryDecorator.java:125) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:58
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten updated an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Change By:
ipleten
We are using gitlab-plugin to pushes statuses back to GitLab server and evaluating gitlab-branch-source-plugin for our need.Pipeline is failing with: " Null pointer exception " and prior that failure in Jenkins maser log:{noformat}...org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")...{noformat}in pipeline we have something like that:{noformat}.. steps {gitlabCommitStatus(STAGE_NAME) { container('deploy') { sh 'mvn deploy' }{noformat}When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an ema
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title
ipleten created an issue
Jenkins / JENKINS-60309
NPE when using with gitlab-plugin's statuses.
Issue Type:
Bug
Assignee:
Parichay Barpanda
Components:
gitlab-branch-source-plugin
Created:
2019-11-27 18:26
Priority:
Minor
Reporter:
ipleten
We are using gitlab-plugin and evaluating gitlab-branch-source-plugin for our need. Pipeline is failing with: Null pointer exception and prior that failure in Jenkins maser log:
...
org.gitlab4j.api.GitLabApiException: Cannot transition status via :run from :running (Reason(s): Status cannot transition via "run")
...
in pipeline we have something like that:
..
steps {
gitlabCommitStatus(STAGE_NAME) {
container('deploy') {
sh 'mvn deploy'
}
When I remove all "gitlabCommitStatus(STAGE_NAME) {" in all stages it starts working.
