[JIRA] (JENKINS-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered I think this has been fixed with v2.4.4 release. PR was https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/172 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-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel edited a comment on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We were also running into this issue and can't merge PRs if the PR was created before the branch build has finished. *In addition*, all builds of branches created from this PR branch are also added to this build list of the PR which totally crashes our development process (might link to https://issues.jenkins-ci.org/browse/JENKINS-55404). See: !InkedImage Pasted at 2019-4-2 12-35_LI.jpg|thumbnail! We are using Jenkins 2.164.1 and BB branch source plugin 2.4.2 and BB 6.1.2 with "Webhook to Jenkins for Bitbucket Server" PluginThank you in advance for the fix! 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-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel updated an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Thomas Kuchel Attachment: InkedImage Pasted at 2019-4-2 12-35_LI.jpg 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-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel commented on JENKINS-55617 Re: No Bitbucket Notification when PR Build is triggered We were also running into this issue and can't merge PRs if the PR was created before the branch build has finished. In addition, all builds of branches created from this PR branch are also added to this build list of the PR which totally crashes our development process (might link to https://issues.jenkins-ci.org/browse/JENKINS-55404). See: We are using Jenkins 2.164.1 and BB branch source plugin 2.4.2 and BB 6.1.2 with "Webhook to Jenkins for Bitbucket Server" Plugin Thank you in advance for the fix! 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-55617) No Bitbucket Notification when PR Build is triggered
Title: Message Title Thomas Kuchel updated an issue Jenkins / JENKINS-55617 No Bitbucket Notification when PR Build is triggered Change By: Thomas Kuchel Attachment: InkedImage Pasted at 2019-4-2 12-35_LI.jpg 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-55404) Wrong merge order of pull request build
Title: Message Title Thomas Kuchel assigned an issue to Antonio Muñiz Sorry for assignment without asking. Could you please have a short look at this issue? Thank you. Jenkins / JENKINS-55404 Wrong merge order of pull request build Change By: Thomas Kuchel Assignee: Antonio Muñiz 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-55404) Wrong merge order of pull request build
Title: Message Title Thomas Kuchel created an issue Jenkins / JENKINS-55404 Wrong merge order of pull request build Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-01-04 12:11 Environment: CentOS 7, Jenkins 2.138.3, bitbucket-branch-source-plugin 2.2.16, Bitbucket Server 5.16.0, Bitbucket Server Jenkins Webhook Plugin Priority: Minor Reporter: Thomas Kuchel When building pull requests in a multibranch pipeline with the Bitbucket branch source plugin, IMO the merge order is wrong. The PR in Bitbucket is set up to merge a task branch into the master branch. The jenkins build console says: Merging remotes/upstream/master commit 49055790acff662de787b04ac7b253140be04b81 into PR head commit 5ea5ad23180c6b9b3c0876fc21f8238a293eb4a0 The problem is that because of the wrong merge order, the commits of the actual task branch aren't shown in the changes "view" (/job//view/change-requests/job//changes). Only the latest master commits are shown. Because of this, the wrong changes are notified to the PR within the Bitbucket server. Can anyone help or am I just configuring something wrong?
[JIRA] [maven-plugin] (JENKINS-26923) Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job
Thomas Kuchel commented on JENKINS-26923 Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy in Maven Job Same here. I'm running 1.580.3 started with "java -jar jenkins.war" call on Windows 7 64-bit running, Maven 3.2.5, jdk1.7.0_67. I have installed just the task-scanner plugin in version 4.44, activated and configured it (files to scan: "src/*/.java"). INFO maven-clean-plugin:2.6.1:clean (default-clean) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-resources-plugin:2.6:resources (default-resources) @ agents-impl INFO Using 'UTF-8' encoding to copy filtered resources. INFO Copying 2 resources WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-compiler-plugin:2.3.1:compile (default-compile) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO INFO maven-surefire-plugin:2.18.1:test (default-test) @ agents-impl ... --- T E S T S --- Running testclass log4j:ERROR Could not connect to remote log4j server at localhost. We will try again later. could not load log4j properties file: /log4j.properties Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 40.608 sec - in de.biotronik.agents.AbstractAgentServiceImplTest Results : Tests run: 11, Failures: 0, Errors: 0, Skipped: 0 WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-jar-plugin:2.5:jar (default-jar) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; INFO INFO maven-source-plugin:2.4:jar (attach-sources) @ agents-impl ... WARNING Failed to notify spy hudson.maven.Maven3Builder$JenkinsEventSpy: org.apache.commons.io.IOUtils.lineIterator(Ljava/io/InputStream;Ljava/nio/charset/Charset;)Lorg/apache/commons/io/LineIterator; I found out that the Tests weren't recorded by Jenkins: Line "JENKINS Recording test results" is missing, so no test result overview is presented when opening the job url. Same happening for other plugins like checkstyle or findbugs... 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/d/optout.
