[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber closed an issue as Fixed Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Resolved Closed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber updated JENKINS-54331 Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Fixed but Unreleased Resolved 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber commented on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Not reproducible anymore with Bitbucket Branch Source Plugin 2.2.15 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber updated JENKINS-54331 Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Torsten Kleiber Status: Open Fixed but Unreleased Resolution: Fixed 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Josiah Eubank commented on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Fixed in 2.2.14 https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/150 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Joseph Petersen assigned an issue to Nikolas Falco Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: Joseph Petersen Assignee: Joseph Petersen Nikolas Falco 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title
dan tran updated an issue
Jenkins / JENKINS-54331
Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Change By:
dan tran
Comment:
actually PR does get receive, but jenkins has error{code:java}// code placeholder{code}Branch event java.lang.NullPointerException at com.fasterxml.jackson.databind.util.ISO8601Utils.parseInt(ISO8601Utils.java:329) at com.fasterxml.jackson.databind.util.ISO8601Utils.parse(ISO8601Utils.java:161) at com.fasterxml.jackson.databind.util.ISO8601DateFormat.parse(ISO8601DateFormat.java:52) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMRevision.(BitbucketGitSCMRevision.java:60) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:843) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:288) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran updated an issue Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: dan tran Comment: Torsten Kleiber does 2.2.14 work out for you?It is not for me.With 2.2.14, new submitted PR does not get built, no build for subsequence commits to the branch. ended up to revert back to 2.2.13, delete the PR and create new one For my production build, we stick with 2.2.12 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran commented on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 actually PR does get receive, but jenkins has error // code placeholder Branch event java.lang.NullPointerException at com.fasterxml.jackson.databind.util.ISO8601Utils.parseInt(ISO8601Utils.java:329) at com.fasterxml.jackson.databind.util.ISO8601Utils.parse(ISO8601Utils.java:161) at com.fasterxml.jackson.databind.util.ISO8601DateFormat.parse(ISO8601DateFormat.java:52) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketGitSCMRevision.(BitbucketGitSCMRevision.java:60) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:843) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:583) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:95) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:288) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Finished: FAILURE 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran edited a comment on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Torsten Kleiber does 2.2.14 work out for you? It is not for me. With 2.2.14, new submitted PR does not get built, no build for subsequence commits to the branch. ended up to revert back to 2.2.13, delete the PR and create new one For my production build, we stick with 2.2.12 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran assigned an issue to Joseph Petersen Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Change By: dan tran Assignee: Joseph Petersen 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title dan tran commented on JENKINS-54331 Re: Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Torsten Kleiber does 2.2.14 work out for you? It is not for me. With 2.2.14, new submitted PR does not get built, no build for subsequence commits to the branch. ended up to revert back to 2.2.13, delete the PR and create new one For my production build, we stick with 2.2.12 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Issue Type: Bug Assignee: Unassigned Attachments: 1_new_plugin_version_two_jenkins_builds.png, 2_new_plugin_only_last_build_update_is_shown_1.png, 3_new_plugin_only_last_build_update_is_shown.png, 4_new_plugin_only_last_build_update_is_shown.png, 5_old_plugin_version_two_jenkins_builds.png, 6_old_plugin_2_builds_of_branch_and_pr_are_shown.png, 7_old_plugin_2_builds_of_branch_and_pr_are_shown.png Components: bitbucket-branch-source-plugin Created: 2018-10-30 07:27 Environment: Jenkins 2.138.2, Bitbucket Branch Source Plugin 2.2.13 Priority: Major Reporter: Torsten Kleiber We use here Bitbucket Merge Checks. We have defined 2 required successful build for merge, one for the branch itself and one for the pull request. This ensure that the master remains clean after the merge. Till 2.2.12 both builds are shown in Bitbucket. From 2.2.13 on only the last branch or pull request build update is shown, so the merge check can never fulfilled anymore!
