[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title Christian Köberl commented on JENKINS-58919 Re: DateTimeParseException on MR web hook the fixed version is now released: https://github.com/gitlab4j/gitlab4j-api/releases/tag/gitlab4j-api-4.12.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201262.156577292.3771.1565932620111%40Atlassian.JIRA.
[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title Christian Köberl commented on JENKINS-58919 Re: DateTimeParseException on MR web hook Yes it worked with GitLab 12.0.x. Anyway the ISO date "2018-03-12T10:16:46+07:00" is valid and should be accepted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201262.156577292.2605.1565781720239%40Atlassian.JIRA.
[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title Christian Köberl updated an issue Jenkins / JENKINS-58919 DateTimeParseException on MR web hook Change By: Christian Köberl Attachment: full-error.html Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201262.156577292.2535.1565773140166%40Atlassian.JIRA.
[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title Christian Köberl commented on JENKINS-58919 Re: DateTimeParseException on MR web hook I already created a PR in gitlab4j which should fix this: https://github.com/gitlab4j/gitlab4j-api/pull/422 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201262.156577292.2533.1565773020665%40Atlassian.JIRA.
[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title
Christian Köberl updated an issue
Jenkins / JENKINS-58919
DateTimeParseException on MR web hook
Change By:
Christian Köberl
When GitLab sends the web hook for a Merge Request Jenkins fails with a 500 (Internal Server Error). The response shows the error is in parsing one of the timestamps:{noformat}java.time.format.DateTimeParseException: Text '2019-08-12T17:08:14+02:00' could not be parsed, unparsed text found at index 22java.time.format.DateTimeParseException: Text '2019-08-12T17:08:14+02:00' could not be parsed, unparsed text found at index 22 at java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:1952) at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1851) at java.time.OffsetDateTime.parse(OffsetDateTime.java:402) at org.gitlab4j.api.utils.ISO8601.toInstant(ISO8601.java:155) at org.gitlab4j.api.utils.ISO8601.toDate(ISO8601.java:169) at org.gitlab4j.api.utils.JacksonJson$JsonDateDeserializer.deserialize(JacksonJson.java:281) at org.gitlab4j.api.utils.JacksonJson$JsonDateDeserializer.deserialize(JacksonJson.java:275) at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:127) at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288) {noformat}This happens since our update to GitLab 12.1 - seems like GitLab now uses this format for "last_commit.timestamp": "2019-08-12T17:08:14+02:00".
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-58919) DateTimeParseException on MR web hook
Title: Message Title Christian Köberl created an issue Jenkins / JENKINS-58919 DateTimeParseException on MR web hook Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-14 08:55 Environment: Jenkins 2.176.2, GitLab 12.1.4 Priority: Minor Reporter: Christian Köberl When GitLab sends the web hook for a Merge Request Jenkins fails with a 500 (Internal Server Error). The response shows the error is in parsing one of the timestamps: java.time.format.DateTimeParseException: Text '2019-08-12T17:08:14+02:00' could not be parsed, unparsed text found at index 22java.time.format.DateTimeParseException: Text '2019-08-12T17:08:14+02:00' could not be parsed, unparsed text found at index 22 at java.time.format.DateTimeFormatter.parseResolved0(DateTimeFormatter.java:1952) at java.time.format.DateTimeFormatter.parse(DateTimeFormatter.java:1851) at java.time.OffsetDateTime.parse(OffsetDateTime.java:402) at org.gitlab4j.api.utils.ISO8601.toInstant(ISO8601.java:155) at org.gitlab4j.api.utils.ISO8601.toDate(ISO8601.java:169) at org.gitlab4j.api.utils.JacksonJson$JsonDateDeserializer.deserialize(JacksonJson.java:281) at org.gitlab4j.api.utils.JacksonJson$JsonDateDeserializer.deserialize(JacksonJson.java:275) at com.fasterxml.jackson.databind.deser.impl.MethodProperty.deserializeAndSet(MethodProperty.java:127) at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:288) This happens since our update to
[JIRA] (JENKINS-58839) NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent
Title: Message Title Christian Köberl commented on JENKINS-58839 Re: NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent The current develop version built by me works without issues. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201154.1565157334000.10512.1565250120189%40Atlassian.JIRA.
[JIRA] (JENKINS-58839) NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent
Title: Message Title Christian Köberl commented on JENKINS-58839 Re: NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent > neither of the objects we are comparing should be null in any case I also looked at the code and yes that seems strange. > Can you retest the plugin by building hpi from the develop branch from repository? Yes I will do that but I'll need until tomorrow. I will also add some logging in the isMatch method. > What gitlab server version are you using? We are running 12.0.4 - but I think this does not matter since the JSON payload looks OK. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.201154.1565157334000.9519.1565168340386%40Atlassian.JIRA.
[JIRA] (JENKINS-58839) NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent
Title: Message Title Christian Köberl created an issue Jenkins / JENKINS-58839 NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-07 05:55 Environment: Jenkins 2.176.2, Linux, Master + 10+ Slaves gitlab-branch-source 0.0.6-beta.5C Priority: Minor Reporter: Christian Köberl We get a NullPointerException on every hook event with the current version of gitlab-branch-source (0.0.6-beta.5C). 07-Aug-2019 07:39:52.137 WARNING [class io.jenkins.plugins.gitlabbranchsource.GitLabMergeRequestSCMEvent Wed Aug 07 07:39:52 CEST 2019 / SCMEvent [#4]] jenkins.scm.api.SCMHeadEvent$DispatcherImpl.log SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.OrganizationFolder$SCMEventListenerImpl@6e03b818 propagated an exception java.lang.NullPointerException at io.jenkins.plugins.gitlabbranchsource.GitLabMergeRequestSCMEvent.isMatch(GitLabMergeRequestSCMEvent.java:59) at io.jenkins.plugins.gitlabbranchsource.AbstractGitLabSCMHeadEvent.isMatch(AbstractGitLabSCMHeadEvent.java:22) at jenkins.branch.OrganizationFolder$SCMEventListenerImpl.onSCMHeadEvent(OrganizationFolder.java:1062) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:246) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:229) at jenkins.scm.api.SCMEvent$Dispatcher.run(SCMEvent.java:505) at
[JIRA] (JENKINS-16748) Build Pipeline Plugin views are not filtered
Christian Köberl created JENKINS-16748 Build Pipeline Plugin views are not filtered Issue Type: Improvement Affects Versions: current Assignee: Daniel Petisme Components: build-pipeline, role-strategy Created: 11/Feb/13 7:30 AM Description: The "Build Pipeline Plugin" (https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin) shows each pipeline as a view. It would be great if this views were filtered by the "Role Strategy Plugin" (https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin) when the user has no right for any job in the pipeline. Currently, the user sees the pipeline view which shows an empty page (because he/she has no rights for any of the jobs). Project: Jenkins Priority: Major Reporter: Christian Köberl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Christian Köberl commented on JENKINS-15156 Builds Disappear from Build History after Completion This seems to happen only with master/slave (multiple nodes) setup. We have a second Jenkins (both 1.489) with nearly the same configuration - the only difference is that this one has no slaves. There the problem does not occur. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Christian Köberl commented on JENKINS-15156 Builds Disappear from Build History after Completion We have the same issue with 1.489. Restarting or reloading config from disk fixes this temporarily. Build history gets lost eventually after the next build. We have master/slave setup with 3 slaves executing jobs (all machines on Linux SLES) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
