[JIRA] (JENKINS-42087) Multibranch pipeline jobs marked dead after SCM event to Git-plugin's notifyCommit endpoint

[peho1...@gmail.com (JIRA)]

Title: Message Title

Peter Horvath created an issue   Jenkins / JENKINS-42087 Multibranch pipeline jobs marked dead after SCM event to Git-plugin's notifyCommit endpoint Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin, git-plugin Created: 2017/Feb/16 9:02 AM Environment: Jenkins 2.32.2 Priority: Major Reporter: Peter Horvath Recently we've upgraded Jenkins to v2.32.2 and all SCM / Branch API 2.x related plugins to the following versions: cloudbees-bitbucket-branch-source 2.1.0 branch-api 2.0.6 cloudbees-folder 5.17 scm-api 2.0.4 git 3.0.5 workflow-multibranch 2.12 Since then multibranch pipeline projects tend to mark specific branches (mostly develop) as dead after processing events from the following endpoint (see. Scan Multibranch Pipeline Events): [Thu Feb 16 08:47:22 CET 2017] jenkins.plugins.git.GitSCMSource$ListenerImpl$1 UPDATED event from _<Bitbucket Server IP>_ ⇒ _<Jenkins Host>_:_<random port>_/git/notifyCommit with timestamp Thu Feb 16 08:47:20 CET 2017 processed in 1.6 sec Such events happen when any other non-multibranch-pipeline jobs get triggered by a Bitbucket Server webhook on the /git/notifyCommit endpoint published by the Git plugin. I guess the bitbucket-branch-source-plugin listens to these events but cannot interpret their payload correctly. SCM environment: Bitbucket Server v4.10.1 Webhook to Jenkins for Bitbucket v3.0.1 (We use the preferred Post Webhooks for Bitbucket v1.2.0 to trigger multibranch-pipeline jobs). Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.