• Type: Bug
• Resolution: Fixed
• Priority: Major
• Component/s: bitbucket-branch-source-plugin
• Labels:

  None

1. 

   Screen Shot 2019-02-03 at 12.21.30 AM.png

   34 kB

   2019-02-02 21:22

2. rebase-target-events.log

   11 kB

   2024-11-27 01:53

3. autosync-fork-events.log

   0.7 kB

   2024-11-27 01:53

[JENKINS-55927] Multibranch pipeline scan is triggered in case of remote pull request merge

Alaiksei Savanchuk created issue - 2019-02-02 21:25

Alaiksei Savanchuk made changes - 2019-02-02 21:26

Summary

Original: Jenkins scan is triggered in case of remote pull request merge

New: Jenkins multibranch pipeline scan is triggered in case of remote pull request merge

Alaiksei Savanchuk made changes - 2019-02-03 06:38

Description

Original: There is such logic in the bitbucket-branch-source plugin:   {{if (push.getChanges().isEmpty()) {}} {{    LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}} {{    newObject[]\{owner, repository});}} {{    scmSourceReIndex(owner, repository);}} }   And this works in case of remote pull request merges.   This leads to reindexing of a multibranch pipeline project which can take a lot of time.

New: There is such logic in the bitbucket-branch-source plugin:    {{if (push.getChanges().isEmpty()) {}}  {{    LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}}  {{    newObject[]\{owner, repository});}}  {{    scmSourceReIndex(owner, repository);}}  }     And this works in case of remote pull request merges.     This leads to reindexing of a multibranch pipeline project which can take a lot of time.   In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our repository only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.

Alaiksei Savanchuk made changes - 2019-02-03 06:57

Description

Original: There is such logic in the bitbucket-branch-source plugin:    {{if (push.getChanges().isEmpty()) {}}  {{    LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}}  {{    newObject[]\{owner, repository});}}  {{    scmSourceReIndex(owner, repository);}}  }     And this works in case of remote pull request merges.     This leads to reindexing of a multibranch pipeline project which can take a lot of time.   In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our repository only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.

New: There is such logic in the bitbucket-branch-source plugin:    {{if (push.getChanges().isEmpty()) {}}  {{    LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}}  {{    newObject[]\{owner, repository});}}  {{    scmSourceReIndex(owner, repository);}}  }     And this works in case of remote pull request merges.     This leads to reindexing of a multibranch pipeline project which can take a lot of time.   In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our Bitbucket multibranch pipeline only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.

Alaiksei Savanchuk made changes - 2019-02-03 08:07

Description

Original: There is such logic in the bitbucket-branch-source plugin:    {{if (push.getChanges().isEmpty()) {}}  {{    LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}}  {{    newObject[]\{owner, repository});}}  {{    scmSourceReIndex(owner, repository);}}  }     And this works in case of remote pull request merges.     This leads to reindexing of a multibranch pipeline project which can take a lot of time.   In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our Bitbucket multibranch pipeline only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotly this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.

New: There is such logic in the bitbucket-branch-source plugin:    {{if (push.getChanges().isEmpty()) {}}  {{    LOGGER.log(Level.INFO, "Received hook from Bitbucket. Processing push event on \{0}/\{1}",}}  {{    newObject[]\{owner, repository});}}  {{    scmSourceReIndex(owner, repository);}}  }     And this works in case of *remote pull request merges.* (https://community.atlassian.com/t5/Questions/Pull-requests-Squashed-commits-Remote-Merges/qaq-p/171569)     This leads to reindexing of a multibranch pipeline project which can take a lot of time.   In my case I have a lot of pull requests(around 150) and build for one of them takes around an hour. These pull requests mostly targeted to the same branch. Because of this we rescan our Bitbucket multibranch pipeline only twice a week because it takes a lot of time to rebuild all of these PRs because the target branch has new changes. And if some pull request is merged remotely this leads to the reindexing which is unexpected. This locks me if this happens in the middle of the day.

Nikolas Falco made changes - 2024-11-08 11:43

Assignee

New: Nikolas Falco [ nfalco ]

Nikolas Falco made changes - 2024-11-22 16:46

Link

New: This issue relates to JENKINS-35674 [ JENKINS-35674 ]

Nikolas Falco made changes - 2024-11-22 16:54

Resolution		New: Not A Defect [ 7 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Allan BURDAJEWICZ made changes - 2024-11-26 21:56

Remote Link

New: This issue links to "CloudBees Internal (Web Link)" [ 30257 ]

Allan BURDAJEWICZ made changes - 2024-11-27 01:53

Attachment

New: rebase-target-events.log [ 63657 ]

Allan BURDAJEWICZ made changes - 2024-11-27 01:53

Attachment

New: autosync-fork-events.log [ 63658 ]

Load more newer history items