Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-23035

Retrigger build all PR after destination branch was changed

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Not A Bug
    • None
    • Jenkins
    • None
    • Maven

    Description

      We can have open many PR in project.

      When destination branch (master in most of case) was changed all waiting PR start build again in the same time - even if no change in PR.

      It cause that build queue can be busy for many hours ....

      PR are checked for "merge commit" it is reason for such behavior.

      Can will be possible to check only hash in PR for changes?

      Examples from Scan Repository log - Maven project:

      Checking pull request #700
      Waiting for GitHub to create a merge commit for pull request 700. Retrying 3 more times...
            ‘Jenkinsfile’ found
          Met criteria
      Changes detected: PR-700 (502bd934976aa7702e07f82b38681e803b58efae+3a5a40c6d23bc4af7ab7945eaac0fa689d2c6143 (91ab40a694de04c4f1488f4ba14c3fdcd9c84a9e) → 502bd934976aa7702e07f82b38681e803b58efae+88d29675ae2a0998d5be134c7941e8fd6aa706bd (8df7060ce5dd0fac46c0e7f2af686b29640baaba))
      Scheduled build for branch: PR-700

      and so on ..

      In this example 8 build was started in the same time concurrently.

      Attachments

        Activity

          People

            humbedooh Daniel Gruno
            sjaranowski Slawomir Jaranowski
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: